Fix defaulting rules to set defaults depending on NATS or EventMesh backend

[grischperl]

Questions:

• Is it possible to do it using the defaulting rules?

Description

• NATS Backend is set as the default
• NATS related backend config values are also defined via defaulting rules (NATSStreamStorageType, etc)
• If the backend is switched to EventMesh, the NATS backend config details remain in the CR and are always recreated upon deletion
• => Defaulting rules for the backend config values need to be different depending on the backend

Acceptance Criteria

• When NATS Backend is set, only NATS related backend config details are automatically set as default
• When EventMesh Backend is set, only EventMesh related backend config details are automatically set as default
• Backend config details not relevant to the active backend can be removed without their recreation

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[grischperl]

This issue can be closed as there is no longer a default backend #274

[grischperl]

/remove-lifecycle stale