Set up an interim fork of the Kubernetes code-gen

[cardil]

After the kubernetes/code-generator#163 issue in Kubernetes code-gen has a PR that is likely to be merged, we should set up an interim fork of that repo.

Such fork would be tracking the Kubernetes code-gen until the said PR be available in Kantive.

The fork should be automatically updated with a CI, to apply our modification on top of the K8s code-gen for each of the release branches.

Our interim drift of K8s code-gen may contain just an embedding of K8s scripts, similar to knative/hack#222

Here are some references which may help set up such a fork:

• RH runs its forks with the https://github.com/cardil/deviate tool, which simplifies the sync process greatly (see example project configuration https://github.com/openshift-knative/kn-plugin-event/blob/main/.deviate.yaml, and the example Jenkins log)
• VMware uses a https://github.com/carvel-dev/vendir tool to sync anything
• Kuberentes is also syncing their monorepo https://github.com/kubernetes/kubernetes onto project specific ones. We might use those tools as well.

[dprotaso]

FYI - this doesn't seem necessary

see: https://github.com/kubernetes-sigs/gateway-api/blob/ee42a6d5d81283d9f41a85627b93e4492b876638/hack/update-codegen.sh#L64

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[cardil]

/reopen
/remove-lifecycle stale
/triage accepted

[knative-prow]

@cardil: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle stale
/triage accepted

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.