change to facet limits

[nocollier]

Proposed change to address #146

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
src/esg_fastapi
__init__.py	2	0	100%
utils.py	31	0	100%
src/esg_fastapi/api
__init__.py	0	0	100%
globus.py	77	0	100%
main.py	15	0	100%
models.py	448	0	100%
routes.py	52	0	100%
types.py	37	0	100%
src/esg_fastapi/configuration
__init__.py	13	0	100%
globus.py	8	0	100%
logging.py	29	0	100%
opentelemetry.py	20	0	100%
profiling.py	15	0	100%
src/esg_fastapi/observability
__init__.py	3	0	100%
main.py	20	0	100%
metrics.py	35	0	100%
models.py	4	0	100%
routes.py	10	0	100%
tests
__init__.py	0	0	100%
conftest.py	15	0	100%
test_app.py	43	0	100%
test_caching.py	45	0	100%
test_esgsearch_parity.py	37	0	100%
test_globus_client.py	90	0	100%
test_metrics.py	35	0	100%
test_models.py	46	0	100%
test_observability.py	47	0	100%
test_settings.py	50	0	100%
test_utils.py	36	0	100%
TOTAL	1263	0	100%

Tests	Skipped	Failures	Errors	Time
84	0 💤	0 ❌	0 🔥	2.389s ⏱️

[nocollier]

Collectively on Slack we decided to pause this merge. From Lee:

All right, I have new information from the Globus Search team.

1. They are deploying a hotfix to increase the limits to a number high enough that our ESGF queries will no longer fail. This will fix the immediate issue and give us some breathing room. I’ll let you know when it’s been deployed so we can confirm the issue is fixed.
2. It turns out, they have been “soft limiting” facet sizes to 5000 all along. So even though we were asking for 2 billion, we were never getting more than 5000. The change today was to add a hard limit on how much you ask for.
3. Globus Search team would like us (ESGF) to change our bridge FastAPI to change the requested facet size from 2 billion to 5000. Because of (2) above, this will not change the behavior we’re seeing in production at all.
4. Just a reminder, we should never be requesting a facet on the id field. (We don’t think anyone is doing that now. this is just a reminder.)