Revamp ContainerRegistry API

[jopemachine]

Follow-up to #1917.

Motivation  

• 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.
• Additionally, 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, and discussions have been held for a more intuitive API design. Let's update the API according to the decision. This will be a breaking change.

Objective  

• Let's update the API according to the decision.

Details  

1. First, let's update the ContainerRegistry API.
2. Next, let's update APIs for adding and removing associations.

Impact  

• The WebUI and ControlPanel client code must be updated accordingly.

[Mizokuiam]

Thank you for raising this issue! I'll look into it and try to help if I can.

[jopemachine]

Thank you for raising this issue! I'll look into it and try to help if I can.

I appreciate your interest in the issue.
But, this issue will include breaking changes and needs to be addressed promptly as a prerequisite for other PRs.

So, I would appreciate it if you could look into other issues instead.