Align runtime-watcher image names

[c-pius]

Description

We use different image names for runtime-watcher in Dev and Prod registries: https://github.com/kyma-project/lifecycle-manager/blob/2ad71ddeb13f42e5a6db022404079f32d6fd8a41/cmd/main.go#L358-L361

Recently, when adapting build pipelines, we confused things up already. We should align the name and use the same for both registries.

Reasons

Consistency and less prone to mistakes

Acceptance Criteria

• [x] agreed on a common name => runtime-watcher (NO -skr suffix)
• [ ] updated pipelines to build the image using the common name
• [ ] updated code to use the image using the common name
• [ ] verify that it works e2e without -skr suffix
• [ ] EDIT CS: consider to update management plane charts to provide the registry value explicitly (as of now it would take the default)

Feature Testing

No response

Testing approach

No response

Attachments

No response

[c-pius]

Prio to be discussed. We may need to have it fixed before the next watcher release.

[c-pius]

updated pipelines to build the image using the common name

watcher is now uniformely built with runtime-watcher name: https://github.com/kyma-project/runtime-watcher/blob/main/.github/workflows/build-image.yml#L41

updated code to use the image using the common name

implementation at KLM side is: https://github.com/kyma-project/lifecycle-manager/pull/1868

See the comments wrt. to the issues with e2e tests

verify that it works e2e without -skr suffix

runtime watcher also needs to be updated to pass the new patch. PR for this is here: https://github.com/kyma-project/runtime-watcher/pull/385