GH workflow has to bump the KIM on KCP DEV automatically at least twice a day (but only if a change happend)

[tobiscr]

Description

We agreed to bump KIM at least twice a day (at least if a change happend since the previous bump) to KCP DEV.

The GH workflow has to be trigger in the morning (e.g. 11 am) and once in the afternoon (e.g. 4 pm) and to

1. Create a new image (Could be done even without using the Neighbors build pipeline by using GH image build features)
2. Bump the image on KCP DEV
3. Run a short smoke test to verify KIM was coming up

AC:

• GH workflow gets automatically triggered at least two time per day
  • If a change happened since the last KIM bump on KCP DEV, the workflow creates a new KIM image
  • the new image is automatically bumped on KCP DEV
  • A simple smoke tests checks if KIM was successfully starting (e.g. quering the metrics endpoint of KIM or checking the health check URL)

Reasons

Avoid to have outdated KIM versions running on KCP DEV.

Attachments

[Disper]

Related automation in KEB https://github.com/kyma-project/kyma-environment-broker/blob/main/.github/workflows/promote-keb-to-dev.yaml