feat: implement configurable enrichment strategy behavior through custom annotation

[TeodorSAP]

Description

Changes proposed in this pull request (what was done and why):

• Implement configurable enrichment strategy behavior through custom annotation
• Add tip in user docs
• Add golden file tests
• Refactor some existing e2e tests
• Implement e2e tests for the new otel enrichment strategy
• Refactor reconcilers' code to avoid duplicated functions
• Simplify update-golden-files Make target

Changes refer to particular issues, PRs or documents:

• Resolves Align Service Name enrichment: Activatable new enrichment logic #2890
• Phase 1 of Align Service Name enrichment #2165

Traceability

• The PR is linked to a GitHub issue.
• The follow-up issues (if any) are linked in the Related Issues section.
• If the change is user-facing, the documentation has been adjusted.
• If a CRD is changed, the corresponding Busola ConfigMap has been adjusted.
• The feature is unit-tested.
• The feature is e2e-tested.

[NHingerl]

Unclear situation whether the feature is already now discouraged (= deprecated) or not. If it's deprecated, let's tackle a deprecation note, which should accompany the update within this doc.
If it's not deprecated yet, this document should not informally act as a pre-deprecation.

[TeodorSAP]

Unclear situation whether the feature is already now discouraged (= deprecated) or not. If it's deprecated, let's tackle a deprecation note, which should accompany the update within this doc. If it's not deprecated yet, this document should not informally act as a pre-deprecation.

I agreed with your initial suggestion to just have it as a tip/option for now. We will make this message stronger in the following phases of the deprecation process, when the default behavior actually changes.