feat: Migrate container registries from etcd to postgreSQL

[jopemachine]

Checklist: (if applicable)

• Milestone metadata specifying the target backport version
• Mention to the original issue
• Installer updates including:
  • Fixtures for db schema changes
  • New mandatory config options
• Test case(s) to:
  • Demonstrate the difference of before/after
  • Demonstrate the flow of abstract/conceptual models with a concrete implementation

Resolves #1907.

Changes

• Migrate container registry schema and data from etcd to PostgreSQL
• Update ContainerRegistry graphql API argument from hostname to id (UUID)
• hostname is changed into registry_name
• Add is_global column to the ContainerRegistry table

[kyujin-cho]

Current implementation does not have a flag field at container_registry table which should indicate if this registry is available for every users. Please update the branch accordingly.

[achimnol]

Is any unhandled exception inside asyncio.run() stored as a queue item?

[jopemachine]

The exception is stored in the queue only when the backup method fails currently.
Should we catch all exceptions occurring in the thread and put them into the queue?

[fregataa]

I left some comments about typing

[fregataa]

Just a little suggestion about type hint in is_known_registry(). How about accepting only dict (or Mapping) type as known_registries parameter?
Please enlighten me how the known_registries looks like in list type and dict type

[jopemachine]

Just a little suggestion about type hint in is_known_registry(). How about accepting only dict (or Mapping) type as known_registries parameter? Please enlighten me how the known_registries looks like in list type and dict type

dict example:

{'stable': {'cr.backend.ai': URL('https://cr.backend.ai')}, 'community': {'cr.backend.ai': URL('https://cr.backend.ai')}, 'multiarch': {'cr.backend.ai': URL('https://cr.backend.ai')}}

list example:

 ['cr.backend.ai']

Note: list is not aware of project unlike dict type here as you see above example.

[fregataa]

good!
in the future, we can apply more strict typing about container image data such as ImageRef, ImageRegistry or ContainerRegistry etc, and revamp codes

[kyujin-cho]

I am postponing milestone to 24.09. We managed to meet our internal deadline for per-user image customization feature (#1973). From now on, at this PR, let's focus on forming concrete definitions and stabilizing things rather than rushing for the merge approval.