feat: proxy customer container registries

[alongubkin]

Stacked on #357.

Adds the least-privilege remote Artifact Registry permission set, Remote Bindings qualification, and the Manager-local OCI broker boundary. Provider credentials remain local and repository lifecycle stays with the management identity.

Validated locally:

• artifact registry permission and preflight suites
• Manager registry broker suite
• Terraform and CloudFormation artifact-registry suites
• Manager binding suite
• cargo check -p alien-manager

[greptile-apps]

Greptile Summary

The PR adds Manager-local proxying for customer container registries while keeping provider credentials inside the Manager and separating data-plane access from repository lifecycle permissions.

• Adds signed, revision-bound customer upload continuations and broker-based OCI authorization.
• Adds remote Artifact Registry bindings and least-privilege AWS, GCP, and Azure permissions.
• Adds provider operations and IaC output needed to manage child repositories and packages.
• Validates the public Manager origin used by customer upload continuations.

Confidence Score: 5/5

The PR appears safe to merge because no blocking failure remains in the previously reported customer upload-continuation paths.

Current HEAD preserves the complete signed customer-session identity, validates it against the current route and repository target, forwards continuation paths with the required OCI prefix, and consistently rewrites customer upload Locations to an explicitly configured Manager origin.

Important Files Changed

Filename	Overview
crates/alien-manager/src/routes/registry_proxy.rs	Adds the customer OCI broker boundary, signed upload sessions, target revalidation, repository translation, and trusted-origin Location rewriting; the previously reported continuation failures are addressed at current HEAD.
crates/alien-manager/src/builder.rs	Wires the optional customer broker, disables automatic upstream redirects, and requires an explicit origin-only Manager base URL.
crates/alien-manager/src/routes/bindings.rs	Adds local Artifact Registry resolution using separate access and management identities without exposing provider credentials over HTTP.
crates/alien-permissions/permission-sets/artifact-registry/remote-read-write.jsonc	Defines the remote Artifact Registry data-plane permissions consumed by generated infrastructure and credential materialization.
crates/alien-cloudformation/src/emitters/aws/artifact_registry.rs	Attaches repository-scoped remote access permissions to the Remote Bindings role while removing lifecycle actions from push credentials.
crates/alien-terraform/src/emitters/gcp/artifact_registry.rs	Extends generated GCP Artifact Registry infrastructure with remote-access qualification and repository-scoped bindings.

Sequence Diagram

sequenceDiagram
  participant Client as OCI Client
  participant Manager as Alien Manager
  participant Broker as Customer Registry Broker
  participant Registry as Cloud Registry

  Client->>Manager: Push customer/repository
  Manager->>Broker: Authorize repository and operation
  Broker-->>Manager: Pinned target and provider binding
  Manager->>Registry: Forward with short-lived provider credentials
  Registry-->>Manager: Upload Location
  Manager-->>Client: Manager-origin signed continuation
  Client->>Manager: PATCH/PUT signed continuation
  Manager->>Broker: Resolve and revalidate signed session
  Broker-->>Manager: Current pinned target
  Manager->>Registry: Forward exact provider session path
  Registry-->>Client: Proxied response

Loading

_{Reviews (22): Last reviewed commit: "test: qualify customer registries on AWS..." | Re-trigger Greptile}