feat:cxar-919 quality gates

[drcgjung]

WHAT

• Debugged the build workflow (wrong foldernames)
• follow release guidelines including chart testing

WHY

• Initial contribution still had TRG violations.
• Actions could not be really tested on catenax-ng fork.

FURTHER NOTES

• The final release branch/workflows (v1.9.5) still need to be setup as main stays on -SNAPSHOT

Largely Closes #5
Closes #20
Closes #19
Merge Hopefully Closes #18

[drcgjung]

@SebastianBezold I really appreciate your help, still struggling a little bit with the chart testing workflow.

"A bit" was tremendously underestimated. Now the lint workflow also builds the docker images, pushes them to the local registry and tests them in the local cluster.

Release mechanism would be as follows:

• Maven/Docker is deployed/published/pushed after push to main or vx.x.x tag
• Helm is released after push to main or release branch

The difference is caused in maven repo typically not allowing to simply "update" existing artifacts (unless they are SNAPSHOTS from main)

[SebastianBezold]

Hi @drcgjung, now worries, we will get that to work :)
Unrelated to that issue, I would kindly ask you to not include the Jira links in your commit messages all the time. Reason:

• This is a closed system, that not everyone in the open-source community has access to
• Information will be lost, as soon as consortium phase is over
• The Link at the beginning of the commit message makes it hard to even see the actual useful info after the link

In best case, the Info, that you are linking to is either included in the PR description itself, or a related GitHub issue.

[SebastianBezold]

LGTM! @drcgjung could you have a look at the comments regarding the additional info for your used Docker base images and decide, if you want to include it in this PR, or open issues for future addition?

[SebastianBezold]

Same as for ontop/ontop we need to provide more info about where to find the original source and so on

[SebastianBezold]

Thanks for the base image info @drcgjung 👍