Add support for optional enum queryables

[Zaczero]

Description:

This enables support for generating "enum" fields for selected queryables. There is also now a concept of optional queryable parameters - so it's possible to indicate enum fields without requiring that field to be present in all collections. This enum generation is very efficient as it's basically an index-only scan.

    "platform": {
      "description": "Satellite platform identifier",
      "title": "Platform",
      "type": "string",
      "enum": [
        "sentinel-2a"
      ]
    },

Other small changes include adding the previously missing get_items_mapping abstract to the base database logic. I also got confused by the existence of "OS_HOST" and "OS_PORT" variables in the Makefile which appear to be unused, so I simply removed them too.

PR Checklist:

• Code is formatted and linted (run pre-commit run --all-files)
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable
• Changes are added to the changelog

[jonhealy1]

Hi @Zaczero Looks great - what do you think about adding a test for this?

[jonhealy1]

Changelog entry

[jonhealy1]

Looks good to me but maybe @jamesfisher-geo or someone else can have a look too.

[jamesfisher-geo]

Looks good! One question in regard to raising a ValueError.

[jamesfisher-geo]

Looks good to me

[jonhealy1]

We shouldn't have to refresh the database in our tests because we add so little data to the db. We could do something like this to refresh as well:

r = await app_client.post(
f"/collections/{collection_id}/items",
json=item_data,
params={"refresh": "true"}
)
r.raise_for_status()

[Zaczero]

It's needed for the tests to pass. After the last item is added, data may not be immediately available for queries (up to a second of delay), which causes tests to be flaky. I don't know a better way to force a refresh, so I just monkey-patched the env config. I tried adding ?refresh=true to the request URL, but that didn't work.

[jonhealy1]

Weird ok

[jonhealy1]

We do add items in other tests that seem to be available immediately

[Zaczero]

In my testing, that wasn't the case, so maybe I'm doing something incorrectly? Some tests pass the refresh=True argument to the db directly (https://github.com/search?q=repo%3Astac-utils%2Fstac-fastapi-elasticsearch-opensearch%20refresh%3DTrue&type=code), which achieves the same goal, but here the tests are hitting the final HTTP endpoint for maximum coverage, and I couldn't find a better way to enforce refresh with it.

[jonhealy1]

It would be nice to document this functionality somewhere as it is potentially very valuable.