Endpoint collections-search/{collection-id} does not work

[YuriZmytrakov]

Describe the bug
Currently, there is no collection-search/{collection-id} endpoint implemented. As a result, it’s not possible to query a single collection through the collections-search endpoint. When attempting to request a specific collection using this route, the API returns an error: {"detail": "Not Found"}
Since the collections/{collection-id} endpoint does not support filters, it’s not possible to restrict user access or limit searches by collection IDs. This means users can still attempt to access collections they don’t have permission for.

Expected behavior
The response should be similar to collections/{collection-id}

[jonhealy1]

I envisioned the /collections-search endpoint as being a for collections version of the /search endpoint which caters to Items. If we add this, then we have to add numerous more api routes which we don't need, because we can just use the /collections route which already exists. /collections-search primarily provides POST search functionality for STAC collections, for Users who can't use POST /collections because they have the Transaction extension enabled, which uses the same route to POST new collections to the database.

[jonhealy1]

Reopen if needed