Add automatic runtime builds to IDE deploy

[miki3421]

What changed

• add generic openserverless.runtimeProfiles support to ops ide deploy
• ensure and poll content-addressed runtime builds before updating actions
• inject the generated image while preserving an explicit action --docker
• rebuild dependent actions when a profile requirements file changes
• generate the system API builder catalog from the versioned runtimes.json
• configure the K3s private registry mirror without requiring Docker
• separate node-side pull and pod-side push registry configuration
• avoid masking errors in the post-deploy setup action lookup

Why

Projects with additional runtime dependencies currently need an out-of-band image build. This keeps the public surface as an ops task and makes ops ide deploy perform the build automatically inside Kubernetes.

The K3s registry setup is idempotent and refuses to overwrite an existing unmanaged registries.yaml.

Impact

Developer machines no longer need Docker for custom runtime builds. The task waits for a successful server-side build and fails before changing the action when the build fails or times out.

This draft is coordinated with changes in openserverless-admin-api, openserverless-operator, openserverless-runtimes, and openserverless-testing. Runtime and image references must be updated before this PR is made ready for review.

Validation

• 10 Bun tests covering profile validation, polling, cache, dry-run, image precedence, K3s registry rendering, and catalog generation
• YAML parsing and git diff --check
• end-to-end deployment on ARM64 Kind/Lima
• end-to-end deployment on ARM64 K3s without Docker
• first build, action invocation, and cached second deploy verified on both clusters