Add stats_counts context api

[acwhite211]

Fixes #7414

Creates a stats_counts api that returns in a json response the counts for collection objects, collections, and specify users. Also, edit the call to the stats server, with these new parameters added. The stats count values are cached for 24 hours in order to not over request to the database.

The lambda function for handling the new stats request is here https://us-east-1.console.aws.amazon.com/lambda/home?region=us-east-1#/functions/AggrgatedSp7Stats?tab=aliases. I also put the lambda function code on discourse https://discourse.specifysoftware.org/t/aggregated-stats-data-lambda-function/3028

The corresponding issue for the stats server to use these new fields is here specify/sp7-stats#7

TODO: Decide what other fields want to be added.

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list

Testing instructions

• Open up the specify home page.
• Look in the dev tools network tab. Check that in the request to the stats contains the new stats counts fields.
• Look in the dev tools network tab. See that the request to the new stats endpoint was successful.

[acwhite211]

Working on fixing the Response body is not available to scripts (Reason: CORS Missing Allow Origin) issue that happens on the test panel.

[acwhite211]

Ok, the CORS Missing Allow Origin issue is resolved on the test panel. Should get a good response now.

[emenslin]

• Look in the dev tools network tab. Check that in the request to the stats contains the new stats counts fields.
• Look in the dev tools network tab. See that the request to the new stats endpoint was successful.

Looks good!

[Iwantexpresso]

• Look in the dev tools network tab. Check that in the request to the stats contains the new stats counts fields.

• Look in the dev tools network tab. See that the request to the new stats endpoint was successful.

[Iwantexpresso]

Found a different issue that sometimes causes an 500 server error to sometimes appear instead of 200. Otherwise, whenever the Get request Responds properly the expected fields and values are there

---

OS: MacOS 26.0.1
Web browser: Firefox
Database: geo_swiss_2025_09_09
Username: spadmin