[Bug]: Incorrect behavior when the nonexistent database name is supplied via the HTTP API

[levand]

What happened?

When using the HTTP API on Chroma Cloud, if a user creates a collection via a POST to /api/v1/collections, but supplies a database parameter that doesn't actually exist (e.g. because of a typo), the request still returns successfully and presents a new collection ID.

However, the new collection doesn't actually exist and subsequent attempts to use the returned ID will fail.

Expected behavior is that the request return a 4XX error with a clear message indicating that the provided database does not exist.

Versions

Chroma Cloud staging

Relevant log output

No response