.WithContainerRegistry has no effect when deploying to Kubernetes

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

Sample code
```
var webFrontend = builder.AddProject("mi-webfrontend")
.WithContainerRegistry(registry); // "mienvacrzbqryxzh6p5lu.azurecr.io"
```
When publishing to Kubernetes with `aspire publish` is producing artefacts which are ignoring the registry URL altogether.

Produced YAML is missing the registry URL and therefore containers have image pull errors
```
parameters:
mi_webfrontend:
port_http: "8080"
port_https: "8080"
mi_webfrontend_image: "mi-webfrontend:latest"

```

### Expected Behavior

Registry URL added to the image in the YAML output

### Steps To Reproduce
Use above code.

### Exceptions (if any)
None

### .NET Version info
10.0

### Anything else?
No

Start by tracing how AddProject and WithContainerRegistry values flow into the Kubernetes output produced by `aspire publish`. Reproduce the sample deployment and inspect the generated YAML, then verify that the container image includes the configured registry URL and no longer causes image pull errors.

Written by the indexing model from the issue text.