Add management support for the multicluster-observability-operator

[periklis]

The following PR prepares the addon to be managed by the multicluster-observability-operator. Two major changes are implemented:

• Support the proposed platform/user-workloads observability capabilities as key-values in the AddonDeploymentConfig.
• Use as a default deployment namespace open-cluster-management-observability

Furthermore the proposed implementation adds validation support in the logging handler for:

• Validate that at least one ClusterLogForwarder pipeline includes infrastructure and/or audit input reference when platformLogsCollection set.
• Validate that at least one ClusterLogForwarder pipeline includes application input reference when userWorkloadLogsCollection set.

The above implementations are not comprehensive but illustrative on how the capabilities defined in the AddonDeploymentConfig can be used within the addon.

[coveralls]

Pull Request Test Coverage Report for Build 9464617973

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 46 of 91 (50.55%) changed or added relevant lines in 3 files are covered.
• 5 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-5.2%) to 57.735%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
internal/addon/helm/values.go	6	10	60.0%
internal/logging/manifests/logging.go	40	47	85.11%
internal/addon/options.go	0	34	0.0%

Files with Coverage Reduction	New Missed Lines	%
internal/addon/helm/values.go	5	45.76%

Totals
Change from base Build 9448258369:	-5.2%
Covered Lines:	209
Relevant Lines:	362

---

💛 - Coveralls

[iblancasa]

Before merging this PR, we need to address some of the comments/questions/concerns that were made in the proposal.

Also, if I understood well, there is a meeting soon that can change the proposal.

[pavolloffay]

Thanks for putting this together and moving from the proposal. I would like to clarify the AddOnDeploymentConfig and how multiple options of the same capability are supported.

[JoaoBraveCoding]

Overall lgtm

[periklis]

Thanks for putting this together and moving from the proposal. I would like to clarify the AddOnDeploymentConfig and how multiple options of the same capability are supported.

The use of multiple values in an AddOnDeploymentConfig will look like this, e.g.:

customizedVariables:
  - name: userWorkloadLogsCollection
    value: clusterlogforwarders.v1.logging.openshift.io;opentelemetrycollectors.v1beta1.opentelemetry.io

translates in the options.go handling to:

case KeyUserWorkloadLogsCollection:
  if keyvalue.Value == string(ClusterLogForwarderV1) {
	  opts.UserWorkloads.Enabled = true
	  opts.UserWorkloads.Logs.CollectionEnabled = true
	  opts.UserWorkloads.Logs.Kinds = append(opts.UserWorkloads.Logs.Kinds, ClusterLogForwarderV1)
  }
  if keyvalue.Value == string(OpenTelemetryCollectorV1beta1) {
	  opts.UserWorkloads.Enabled = true
	  opts.UserWorkloads.Logs.CollectionEnabled = true
	  opts.UserWorkloads.Logs.Kinds = append(opts.UserWorkloads.Logs.Kinds, OpenTelemetryCollectorV1beta1)
  }					

Note: This is just pseudo-code and not meant to be implemented in this PR yet. I am leaving the room open for you guys to add support for multiple values when you are ready with each signal. WDYT?

[pavolloffay]

LGTM (after we clarified