catalogd web api benchmarking

[grokspawn]

1. Establish a common access pattern for assessing performance of the catalogd query web API for e.g.
   • initial catalog data unpack (index preparation)
   • catalog data update & re-unpack
   • query[-no-parameters-],
   • query&name=$somePackage&schema=olm.package,
   • query&package=$somePackage
2. Collect pprof profiles for CPU and memory when evaluating the pattern
3. Find the most resource intensive code paths. Provide documentation and recommendations related to making improvements in those areas.
4. Coordinate with OLM maintainers to make improvements in areas deemed to provide the most significant performance and scale gain.
5. Implement automated performance and scale regression tests in the existing upstream CI test suite.

[grokspawn]

We want to include this scope in #920. I'd initially argued that we would want to scope 920 over existing APIs and performance evaluations and use this for just the query API, but in discussion now this really ought to be considered part of the scope associated with 920. I'll adjust the body there to include it.

[github-actions]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.