Make sure static.yaml is up to date with output of make manifests

[lubronzhan]

What this PR does / why we need it:

static.yaml should be consistent with output of make manifests

it shouldn't contain the ako-operator manifest, as you can see in ytt-manifest target, it's applied along with ako-operator.yaml.

# Generate manifests e.g. CRD, RBAC etc.
manifests: $(CONTROLLER_GEN) $(KUSTOMIZE)
	$(CONTROLLER_GEN) $(CRD_OPTIONS) rbac:roleName=manager-role webhook paths="./..." output:crd:artifacts:config=config/crd/bases
	$(KUSTOMIZE) build config/kustomize-to-ytt > config/ytt/static.yaml

# Generate manifests from ytt for AKO Operator Deployment
.PHONY: ytt-manifests
ytt-manifests: $(YTT)
	@$(YTT) -v imageTag=$(BUILD_VERSION) -f config/ytt/ako-operator.yaml -f config/ytt/static.yaml -f config/ytt/values.yaml

Should rerun it once golang is bumped
Which issue(s) this PR fixes:

Fixes #

Describe testing done for PR:

Special notes for your reviewer:

Release note:

New PR Checklist

• Ensure PR contains only public links or terms
• Use good commit messages
• Squash the commits in this branch before merge to preserve our git history
• If this PR is just an idea or POC, use a Draft PR instead of a full PR
• Add appropriate labels according to what type of issue is being addressed.

[christianang]

I did notice that a set of resources was removed in the static.yaml by the regeneration, but I'm assuming those are no longer necessary and they were removed earlier by whatever PR forgot to regenerate.

Approved.

[lubronzhan]

Yeah it shouldn't contain the ako-operator manifest anymore, as you can see in ytt-manifest target, it's applied along with ako-operator.yaml.

# Generate manifests from ytt for AKO Operator Deployment
.PHONY: ytt-manifests
ytt-manifests: $(YTT)
	@$(YTT) -v imageTag=$(BUILD_VERSION) -f config/ytt/ako-operator.yaml -f config/ytt/static.yaml -f config/ytt/values.yaml