WIP: OKD-259: Validate OKD featureset to prevent it from being enabled on OCP clusters

[jatinsu]

What type of PR is this?

/kind feature
/kind api-change

What this PR does / why we need it: It allows the kubernetes repo to be built with a scos tag which will be used to validate if a cluster is a OCP or OKD cluster. This is to prevent users from enabling the OKD featureset if they happen to be on a OCP cluster

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Added: OKD featureset and OKD featureset validation 

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

https://github.com/openshift/api/pull/2451

[openshift-ci-robot]

@jatinsu: This pull request references OKD-259 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.20.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature
/kind api-change

What this PR does / why we need it: It allows the kubernetes repo to be built with a scos tag which will be used to validate if a cluster is a OCP or OKD cluster. This is to prevent users from enabling the OKD featureset if they happen to be on a OCP cluster

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Added: OKD featureset and OKD featureset validation 

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

https://github.com/openshift/api/pull/2451

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@jatinsu: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 2d04a2c|Added basic validation for OKD featureset: does not specify an upstream backport in the commit message
• 87b2e70|Added validation to check if a image is being built for OKD: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jatinsu
Once this PR has been reviewed and has the lgtm label, please assign deads2k 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:

• DOWNSTREAM_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-robot]

@jatinsu: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 278fb30|Revert docker image change: does not specify an upstream backport in the commit message
• 2d04a2c|Added basic validation for OKD featureset: does not specify an upstream backport in the commit message
• 87b2e70|Added validation to check if a image is being built for OKD: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.