Force enable restricted access on contract overages allowed false

What does this MR do and why?

When the custom attribute contract_overages_allowed is set to false on a Self-Managed license or a GitLab.com subscription, then we force-enable restricted access for the instance or namespace.

References

• Contributes to Show Restricted Access status and inform about ... (#580284)

Screenshots or screen recordings

- Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Deployment Type	URL	Before	After
GitLab.com	http://gdk.test:8080/groups/15026/-/edit#js-permissions-settings
Self-Managed	http://gdk.test:8080/admin/application_settings/general#js-signup-settings

How to set up and validate locally

• Start your CustomersDot

GitLab.com

1. Start your GitLab instance in SaaS mode export GITLAB_SIMULATE_SAAS=1; gdk restart
2. Get a subscription for a top-level group
3. Check that http://gdk.test:8080/groups/15026/-/edit#js-permissions-settings shows the Restricted Access controls
4. Set the custom attribute contract_overages_allowed__c for your subscription to false via Zuora and sync the subscription to GitLab
5. Check that http://gdk.test:8080/groups/15026/-/edit#js-permissions-settings hides the Restricted Access controls

Self-Managed

1. Start your GitLab instance in Self-Managed mode export GITLAB_SIMULATE_SAAS=0; gdk restart
2. Get and enable a license for your instance
3. Check that http://gdk.test:8080/admin/application_settings/general#js-signup-settings shows the controls
4. Set the custom attribute contract_overages_allowed__c for your license to false via Zuora and sync the license to GitLab
5. Check that http://gdk.test:8080/admin/application_settings/general#js-signup-settings hides the controls