feat: add remaining resource usage to instance stats

[thomasheartman]

Updates the instance stats endpoint with

• maxEnvironmentStrategies
• maxConstraints
• maxConstraintValues

It adds the following rows to the front end table:

• segments (already in the payload, just not used for the table before)
• API tokens (separate rows for type, + one for total) (also existed before, but wasn't listed)
• Highest number of strategies used for a single flag in a single environment
• Highest number of constraints used on a single strategy
• Highest number of values used for a single constraint

Discussion points

Do we want a flag for this? It seems like an innocuous change and it's made to go with soft limits, so I'm not sure I want to add another flag for it. At the same time, we can probably leave this change in beta for another cycle and add it in later. We can also choose to flag only the front end or both the front end and the back end.

Do we expect these queries to cause any kind of degradation in performance?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
unleash-monorepo-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 22, 2024 8:59am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
unleash-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 22, 2024 8:59am

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Manifest Files

[thomasheartman]

All the switches from number => integer here are optional. These are integers, though, so it makes the schema more correct, but we can take 'em out if wanted.