Separating route securities from other dependencies.

[rhysrevans3]

Related Issue(s):

• Allow multiple security dependency per route  #765

Description:
Currently if you have more than one security dependency on a single route, if either fail then the route will be unauthorised. This is a known issue in FastAPI and the suggested solution is to use a single dependency to merge the sub dependencies. This makes configuration more difficult and removes the ability to use default security dependencies.

Suggested solution is to separate route securities from other dependencies. This then allows them to be merged when dynamically.

There are two options for merging in this pull request.

merge_dependencies1 uses the traditional merging method but this requires dependencies return a value or None rather than raise an error. This means it would need to be used for all routes even those without multiple dependencies.

merge_dependencies2 calls each dependency itself which allows them to raise their own errors so can be used only on routes that have multiple dependencies.

PR Checklist:

• pre-commit hooks pass locally
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
• Changes are added to the CHANGELOG.

[rhysrevans3]

Moving to stac-fastapi-elasticsearch-opensearch see issue #765 for details.