Canonical K8s provider does not configure local registry

Unlike the microk8s provider, the k8s provider used in `integration_test_run.yaml` does not configure local registry. This makes PR from forked repository cannot push the built rock image to local registry, and the workflow will fail with something like this:

```text
/usr/bin/skopeo copy --insecure-policy --dest-tls-verify=false oci-archive:/tmp/artifact-bxCRMt/falcosidekick_2.32.0_amd64.rock docker://localhost:32000/falcosidekick:2.32.0_amd64.rock
Getting image source signatures
Copying blob sha256:20043066d3d5c78b45520c5707319835ac7d1f3d7f0dded0138ea0897d6a3188
Copying blob sha256:2ffda389e4107f4d3cd23cdbbdf763fa5257eaf67740d698a6c0a08fd90daf22
Copying blob sha256:c0f9d5abd2c81e4c75549fbaeb99bba2c031caf12c684ad866225b286f5bdcf8
Copying blob sha256:f3d5189ccbed27f076564ca35094887aa0698290a8f0079c07a9d974fcf446ff
time="2025-12-15T10:30:40Z" level=fatal msg="trying to reuse blob sha256:20043066d3d5c78b45520c5707319835ac7d1f3d7f0dded0138ea0897d6a3188 at destination: pinging container registry localhost:32000: Get \"http://localhost:32000/v2/\": dial tcp 127.0.0.1:32000: connect: connection refused"
```

Note, this is not a problem for microk8s provider, since microk8s enables `registry` addons. We need something similar in k8s provider.