[epic] catalogd web interface performance improvements

[grokspawn]

The RFC written for operator-framework/catalogd#426 identified a desire to formalize the catalogd web API, and divided work into a set of v1.0-blocking changes to enable versioned web interfaces (phase 1) and non-blocking changes to express and extend a formalized API specification (phase 2).

This epic is to capture the need to provide more performant FBC access APIs. Initial work captured here intended to provide for API discovery via an OpenAPI endpoint is split off to #1568.

Work here will be behind a feature gate.

• catalogd web api performance improvements RFC #1569
• implementing feature-gated, caching catalogd web query API #1603
• serve catalog content based on supplied parameters #1606
• catalogd: Query end point does not support range requests #1696
• catalogd: Unit tests for indexing algorithm. #1697
• catalogd web api unit test misc fixes #1709
• 🌱 (catalogd) add unit tests for indexing algo for query endpoint #1702
• ⚠ (catalogd) Update query endpoint to metas endpoint #1703
• 🐛 (catalogd) Don't write to header after checking for Preconditions #1710
• 🌱 (catalogd) add more unit tests for localdir storage.Instance #1713
• [docs] update catalogd web api docs to include metas endpoint #1782
• [docs] update catalogd component-internal web api docs, demos #1783

[grokspawn]

note: we have discrete api discovery and package discovery, but the original description conflates them. Clean up.

1. parametric query interface to drill down
   1. v1/query to start with
2. carve off API discovery (e.g. swagger endpoint discovery) to a separate v1.x-scoped epic.