fix default-apps app template generation

[bavarianbidi]

What does this PR do?

(Please set a descriptive PR title. Use this space for additional explanations.)

What is the effect of this change to users?

--- .vscode/generated-manifest-current.yaml	2023-05-15 15:54:05.392431214 +0200
+++ .vscode/generated-manifest-new.yaml	2023-05-15 15:59:43.863036035 +0200
@@ -62,14 +62,15 @@
 metadata:
   labels:
     app-operator.giantswarm.io/version: 0.0.0
+    giantswarm.io/cluster: jrp45
   name: jrp45-default-apps
   namespace: org-multi-project
 spec:
   catalog: cluster
   config:
     configMap:
-      name: ""
-      namespace: ""
+      name: jrp45-cluster-values
+      namespace: org-multi-project
     secret:
       name: ""
       namespace: ""

What does it look like?

(Please add anything that represents the change visually. Screenshots, output, logs, ...)

Any background context you can provide?

Towards the kube-proxy replacement powered by Cilium

What is needed from the reviewers?

Without the auto-generated -cluster-values configmap, the mandatory baseDomain value doesn't get propagated to the cilium config which is required to run in kube-proxy-less mode.

Do the docs need to be updated?

Should this change be mentioned in the release notes?

• CHANGELOG.md has been updated

Is this a breaking change?

(Breaking changes are, for example, removal of commnds/flags or substantial changes in the meaning of a flag. If yes, please add the breaking-change label to the PR.)

[primeroz]

LGTM. can you add an example run of kubectl gs template ?

[bavarianbidi]

LGTM. can you add an example run of kubectl gs template ?

it's already documented in our public docs:
https://docs.giantswarm.io/getting-started/capz-cluster-creation/