refactor: migrated to upstream chart and did a lot of other things

[Michael-Kruggel]

• Closes May template Keycloak fields to provide flexibility for delivery customers to configure. #13
• Closes Should limit the use of Zarf variable templates and prioritize configuring packages via Helm value overrides #15
• Closes May template network policy keys to provide flexibility for delivery customers to configure. #8
• Closes Should name the client <App> Login (i.e. Mattermost Login) to provide login UX consistency. #10
• Closes Should clearly mark the client id with the group and app name uds-<group>-<application> (i.e. uds-swf-mattermost) to provide consistency in the Keycloak UI. #11
• Closes Should implement or allow for multiple flavors (ideally with common definitions in a common directory) #14
• Closes Must be maintained by a resourced team that is explicitly defined as maintaining the project (i.e. in CODEOWNERS) #18
• Closes Refactor to use upstream chart #32

[JoeHCQ1]

Confluence has a createContainerConfigError - @Michael-Kruggel looks like you may have run into the same problem I had.

[Michael-Kruggel]

Yeah @JoeHCQ1, its due to the awkward nature of the upgrade test. Instead of checking out the latest tag and deploying that, it takes the most recent package and then tries to deploy that using your changes.

Upgrade upstream would never work because there is not an upstream flavor to upgrade from.

Note: I checked-out main, deployed the cluster and package using uds run default. I then checked-out this branch, and deployed just the package using uds run dev, and it came up healthy.

[corang]

confirmed test from @Michael-Kruggel