refactor(BA-483): Revamp ContainerRegistryNode API

[jopemachine]

Resolves #3418 (BA-483).

Outlines

Caution

This PR include breaking change.

This PR performs the following tasks:

• In PR feat: Migrate container registry config storage from Etcd to PostgreSQL #1917, there was some confusion as the ContainerRegistryNode API was changed to no longer use graphene.InputObjectType. Let's revert to using graphene.InputObjectType for accepting arguments.

• PR feat(BA-463): Implement APIs for associating, disassociating container_registries with groups #3067 implements an API to establish the relationship between container_registries and groups. It removes the undocumented APIs and adds new ones.

GQL example

Refer to the schema.graphql file to see how the input types for each GQL query and mutation have changed.
In this section, I will explain each GQL usage with examples.

create_container_registry_node

mutation {
  create_container_registry_node (props: { type: "harbor2", registry_name: "cr.backend.ai", url: "https://cr.backend.ai", project: "stable", allowed_groups: { add: ["2de2b969-1d04-48a6-af16-0bc8adb3c831"] } }) { 
    container_registry {
      id
      row_id
      name
    }
  }

modify_container_registry_node

mutation {
  modify_container_registry_node (id: "5c7090ca-0422-4ed6-86c1-7bba2a5de153", props: { registry_name: "cr.backend.ai2", url: "https://abcdef", project: "", allowed_groups: { remove: ["2de2b969-1d04-48a6-af16-0bc8adb3c831"] } }) {
    container_registry {
      id
      row_id
      name
    }
  }
}

delete_container_registry_node

mutation {
  delete_container_registry_node (id: "5c7090ca-0422-4ed6-86c1-7bba2a5de153") {
    container_registry {
      id
      row_id
      name
    }
  }
}

allowed_groups

query {
  container_registry_node(id: "<encoded registry_id>") {
    allowed_groups (limit: 5, offset:0) {
      name
      created_at
    }
  }
}

---

Checklist: (if applicable)

• Milestone metadata specifying the target backport version
• Mention to the original issue
• API server-client counterparts (e.g., manager API -> client SDK)
• Test case(s) to:
  • Demonstrate the difference of before/after
  • Demonstrate the flow of abstract/conceptual models with a concrete implementation
• Documentation
  • Contents in the docs directory
  • docstrings in public interfaces and type annotations

---

📚 Documentation preview 📚: https://sorna--3424.org.readthedocs.build/en/3424/

---

📚 Documentation preview 📚: https://sorna-ko--3424.org.readthedocs.build/ko/3424/

[jopemachine]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(BA-143): Implement Image Rescanning using Harbor Webhook API #3116
• feat(BA-145): Implement CRUD API for managing Harbor per-project Quota #3090
• feat(BA-512): Implement ImageNode, ImageNodes as per-project images API #3036
• feat(BA-464): Implement Image RBAC project scope #3035
• refactor(BA-483): Revamp ContainerRegistryNode API #3424 👈 (View in Graphite)
• feat(BA-463): Implement APIs for associating, disassociating container_registries with groups #3067
• feat(BA-147): Implement m2m table for container_registries, and groups #3065
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[fregataa]

In our RBAC system, target scope should not be null. You can use SystemScope if you need to query in a system wide scope.

[fregataa]

Just an idea. Since we are likely to have more orthogonal scopes mapped to project scopes, we could define a parameter type that contains container_registry_scope and use it here.
e.g.

@dataclass # Can replace this with pydantic, TypedDict whatever you want!
class ProjectAdditionalScope:
    container_registry_scope: Optional[ContainerRegistryScope] = None

async def get_connection(
        cls,
        info: graphene.ResolveInfo,
        scope: Optional[ScopeType] = None,
        extra_scopes: ProjectAdditionalScope,