Generate manifests using Helm

[ciarams87]

Proposed changes

Problem: As a potential user of NKG
I want the manifest files simplified in the deployment manifests folder in the NKG repo
So that when I install NKG using manifests, I am not hindered by the need to evaluate each manifest file to see what is relevant to deploy for my environment.

Additionally, now that we have Helm templates, we have multiple deployment manifests/ templates requiring maintenance. This carries the risk of one of the deployment methods becoming out-of-sync with the other.

Solution: Generate the deployment manifests from the Helm templates, simplifying maintenance, and reducing the required steps a user needs to undertake to deploy NKG using manifests. This also has the effect that labels and selectors are consistent across the Helm templates and the manifests.

This solution does not include the Service manifest in the main manifest yaml as this is environment specific. However, the Service manifests are also generated from the Helm templates.

Additionally, the static deployment manifest for the provisioner is also being generated, and has been moved to the conformance/provisioner folder with the provisioner yaml.

Testing: Manual installs using Helm and the new manifests, and ensuring the conformance tests can still run and pass

Closes #780

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[pleshakov]

👍

[kate-osborn]

🚀