Automated release process for ACM

[koala7659]

Description

After consolidating the ACM module, we have to review the release process.

AC:

• ACM module can be released with one click
• Version has to be assigned properly (following semantic versioning pattern of Kyma, see Use semantic versioning for kyma modules (managers) kyma#18410)
• Test that the non-managed installation of the ACM module works properly by applying YAML via kubectl (see https://kyma-project.io/#/02-get-started/01-quick-install)
• Review release documentation for ACM and update it to match with the latest release process

Relates to

• Implement DORA metrics measuring in AC delivery pipeline #201
• Automate assets attachment during release process #105
• Use semantic versioning for kyma modules (managers) kyma#18410

Please consider also this bug: YAML manifests have to be populated as asset to the generated Github release (#325)

[tobiscr]

Please verify if we can generate synergy effects by combining this issue with #135

[tobiscr]

Feedback from @koala7659 after release ACM 1.1.7:

App connector 1.1.7 release process is horrible experience. It should not take more than few hours to make new release and test it. Two days should be max. I couldn't release it during a week. Imagine we have critical bug on production and we say we need one week to release the fix. Here are some problems I identified:

• The code had lot of tech debt (old dependencies, GH
  actions to update, cross dependencies between components)
• Waiting for checkmarx approval
• The build artifacts could not be built without fixing GH Actions
• Executable from Kaniko was corrupted (should already be fixed by Neighbors)
• Problem with tests on Kyma cluster
• Release documentation not valid https://github.tools.sap/kyma/module-manifests/Readme.md - still I must figure out the way to test it.