As a follow-up to RHCLOUD-40138 we should consider making this a configurable setting per organization to allow certain customer deals where some orgs may need more than the default number of workspaces.

This may warrant a design doc/spike, but here are some ideas to start with:

Option 1: Use Unleash (requires this PR) to have "WORKSPACE_ORG_CREATION_LIMIT" (from this PR) driven by feature flags supplying context fields for the org id, with a default value. This would be the least invasive approach, requiring the least amount of overhead. Given that this will be a customer-driven request, that may be the best approach. One downside is that this may be misusing Unleash in that it would be expected to be a long-term configuration vs a feature flag. For that reason, it may not be the best approach.

Option 2: Store some configuration object(s) in the DB for Tenant records. We'd need a way to update these (maybe a Turnpike UI eventually?). We'd likely want it to be generic, or able to support multiple types of configuration records per Tenant, so that we could extend it for not just overall workspace limits, but depth limits, etc., moving forward. This would be the most durable, extensible, but also most invasive option.