bug: Self-hosted local push gets registry_not_supported (CLI 4.4.0+)

[isshaddad]

Provide environment information

CLI 4.4.0+

Describe the bug

When deploying with local Docker push against a self-hosted Trigger webapp (CLI 4.4.0+), the CLI requests registry credentials from the webapp, which returns registry_not_supported because the webapp only supports AWS ECR (amazonaws.com). Local push used to work with CLI < 4.4.0.

Expected: Local push either uses local Docker auth and does not call the webapp for credentials, or the webapp supports non-ECR registries for self-hosted.

Workaround: set TRIGGER_DOCKER_USERNAME and TRIGGER_DOCKER_PASSWORD so the CLI skips the webapp.

Reproduction repo

n/a

To reproduce

1. Self-host Trigger webapp.
2. Use CLI 4.4.0+ and deploy with local Docker push (no remote builder).
3. Do not set TRIGGER_DOCKER_USERNAME / TRIGGER_DOCKER_PASSWORD.
4. CLI calls webapp for registry credentials; webapp returns registry_not_supported (deployment image ref is not ECR).
5. Deploy fails. With CLI < 4.4.0 or with TRIGGER_DOCKER_* set, it succeeds.

Additional information

No response