[Feature Request]: API authencation (Basic, Token,...)

### Describe the problem

Hi team,
I deployed chroma as docs [here](https://docs.trychroma.com/production/containers/docker) with authencation as below:
````
environment:
- IS_PERSISTENT=TRUE
- PERSIST_DIRECTORY=./chroma
- ANONYMIZED_TELEMETRY=TRUE
- CHROMA_OPEN_TELEMETRY__ENDPOINT=http://otel-collector:4317/
- CHROMA_OPEN_TELEMETRY__SERVICE_NAME=chroma
- CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER=chromadb.auth.token.TokenConfigServerAuthCredentialsProvider
- CHROMA_SERVER_AUTH_PROVIDER=chromadb.auth.token.TokenAuthServerProvider
- CHROMA_SERVER_AUTH_TOKEN_TRANSPORT_HEADER=X_CHROMA_TOKEN
- CHROMA_SERVER_AUTH_CREDENTIALS=test
````
I used sample code as below but authencation seem not worked (still connect normal without authencation):
```
import chromadb

client = chromadb.HttpClient(host="localhost", port=8000)
collection = client.create_collection(name="example_collection")
```
Or not work for [VectorAdmin ](https://github.com/Mintplex-Labs/vector-admin) (API Header and Key).

Is there any info that setup docker compose for authencation?

### Describe the proposed solution

I' m finding how to deploy chroma having API authencation as customized chroma [here](https://blog.amikos.tech/secure-your-chroma-db-instance-part-1-authentication-c2f1979e7c19) but it's not offical.

Maybe contact to customized chroma author to develop for this feature.

### Alternatives considered

I hope this feaure that release offical in the feature.

### Importance

nice to have

### Additional Information

_No response_

Start with the linked Docker deployment documentation and the Python chromadb.HttpClient entry point shown in the report. Reproduce the configured token-authentication setup, determine why unauthenticated requests still succeed, and define the supported Basic or token configuration and client behavior before implementation.

Written by the indexing model from the issue text.