[feat] support multiple image registries in stacks

[marchrius]

I want to explicitly point out that I used Codex 5.5 for this task.

Summary

Ref. #496
Adds support for configuring multiple Docker image registries on Stack resources.

Previously, Stacks supported a single registry_provider / registry_account pair for logging in before docker compose / docker stack operations. This change introduces image_registry on StackConfig, allowing multiple registry/account pairs to be selected and used during stack pull, deploy, and run flows.

Changes

• Add image_registry: Vec<ImageRegistryConfig> to StackConfig.
• Keep backward compatibility with existing registry_provider / registry_account fields.
• Update Stack configuration UI to manage multiple registry/account rows.
• Resolve and pass multiple registry tokens from Core to Periphery.
• Update Periphery stack login logic to login to all configured registry/account pairs.
• Update Compose and Swarm stack API payloads from a single registry_token to registry_tokens.
• Update generated TypeScript client types.

Compatibility

Existing Stacks using registry_provider / registry_account continue to work.

In the UI, legacy single-registry config is shown as a single registry row. When the Stack config is saved through the new UI, the value is written to image_registry and the legacy fields are cleared.

Validation

Tested locally with:

cargo fmt
cargo check -p komodo_client -p periphery_client -p komodo_core -p komodo_periphery
cd ui && yarn build

Screenshots:

Configurations

Download success

Download failed