The dependency proxy settings GraphQL API

⛓ The GraphQL API for the dependency proxy settings

The frontend will need to access to the dependency proxy settings of a project (read, write).

For the dependency proxy settings, we will follow what we have for the dependency proxy for container images:

• A GraphQL query to read the settings out of a project. Default values are returned if the setting doesn't exist.
• A GraphQL query to update the settings. The setting object is created if it doesn't exist.

Please note that if the settings doesn't exist for a project, we will return default values. This allows us to create (and store) the settings object only when needed.

For permissions, use admin_dependency_proxy: granted to users with at least maintainer access level.

🔭 The Plan

From the investigation:

1. Database model for the dependency proxy settings (#410714 - closed).
2. The Maven dependency proxy API: cache hit path (#410717 - closed).
3. The Maven dependency proxy API: cache miss path (#410719 - closed).
4. The dependency proxy API skeleton for Maven pac... (#410721 - closed).
5. The dependency proxy settings API. (👈 this issue)
6. Dependency proxy for Maven: frontend changes (#410726 - closed)
7. (Option) Dependency proxy for Maven: the prefill option (#410730 - closed).
8. Document the dependency proxy for Maven (#410731 - closed)