[BUG] fix chroma api auth

[philipithomas]

Philip here from the Chroma team.

This SDK currently authenticates via a bearer token.

However, Chroma uses the x-chroma-token header instead of bearer, leading all authenticated requests with this SDK to fail with a 401 error. (Details in the Chroma OpenAPI spec: https://api.trychroma.com/docs/ )

I've patched the authentication method in this PR.

[ilayaperumalg]

@philipithomas Thanks for the PR!

@Kehrlann Could you review the changes please? Thanks!

[philipithomas]

@Kehrlann Happy to help set up a free Chroma Cloud org for E2E testing, whether manual or automated - my email is philip at trychroma.com.

[Kehrlann]

Thanks for the contribution @philipithomas ! The fix seems correct.

[question] I'm a bit confused as to why the TokenSecuredChromaWhereIT does not fail with the current setup. Can you try it on your machine, and try to reproduce?
Is it because it's an outdated Chroma image?
It'd be good to have this correctly covered by tests.

[suggestion, non-blocking] One nice-to-have, good opportunity for a small refactoring. Instead of capturing the token in ChromApi#withToken, we do something similar to ChromaApi#withBasicAuthCredentials, something like:

public ChromaApi withKeyToken(String keyToken) {
	this.restClient = this.restClient.mutate()
			.defaultHeader(X_CHROMA_TOKEN, keyToken)
			.build();
	return this;
}

And we remove both the keyToken field and the httpHeader method.

[Kehrlann]

Consider putting x-chroma-token in a static field.