Investigate nomenclature of settings for interim solution

Problem to investigate

Collections have be redefined in groups and projects ( https://gitlab.com/gitlab-org/gitlab/-/issues/393190#outstanding-questions-to-answer), which don't directly align with the options provided under settings.

• Do they need to match 1:1? CI/CD vs Build
• How can similar page names be differentiated? Repository vs Repository

Comparison

	Group	Project	MVC
✔️️	General	General
✔️	Integrations	Integrations
✔️	Webhooks	Webhooks
✔️️	Access Tokens	Access Tokens
❓️	Projects	N/A
⚠️️	Repository	Repository	Repository settings
⚠️️	N/A	Merge requests	Merge request settings
❓	CI/CD	CI/CD
✔️️	Applications	N/A
❓	Packages and registries	Packages and registries
✔️️	N/A	Pages
⚠️️	N/A	Monitor	Monitor settings
✔️️	Usage Quotas	Usage Quotas
✔️️	SAML SSO 🚩	N/A
✔️️	SAML Group Links 🚩	N/A
✔️	Billing	N/A
✔️	Domain verification	N/A
✔️	LDAP Synchronization	N/A

• ✔️️ unique name, not necessarily the best
• ⚠️️ conflicting name
• ❓ confusing name
• 🚩 Behind a feature flag

Comparison

Security uses configuration, but this would cause truncation when paired with merge requests.

+settings	+configuration