WIP: Server side configuration of must gather enhancement

[MarSik]

The idea is to allow configuration of must gather via an object deployed to
a cluster. This allows better match to specific data collection needs based
on the purpose of the cluster and avoids human mistakes when running must-gather
manually.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign cybertron for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@MarSik: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/markdownlint	c8acfb5	link	true	/test markdownlint

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[MarSik]

TODO Describe the https://github.com/openshift/must-gather-operator differences.

• they define Kind: MustGather
• requires a cluster operator which is problematic for some use cases (SNO)
• I need to take a better look at it to see the features and differences