feat(ws): initial commit for controller

[jiridanek]

cd workspaces/controller
go mod init github.com/kubeflow/notebooks/workspaces/controller
kubebuilder init \
    --plugins=go/v4 \
    --domain=kubeflow.org \
    --project-name=workspace-controller \
    --repo=github.com/kubeflow/notebooks/workspaces/controller
kubebuilder create api --version v1beta1 --kind Workspace
kubebuilder create api --version v1beta1 --kind WorkspaceKind
make manifests

TODO:

• think about the branch patterns for GHA triggering (add release branches?)
• integration test with kind (kubeflow/kubeflow notebooks controller has that)
  • separate PR, I'd prefer to merge this scaffold separately from that
  • ci(ws): add integration test that deploys workspace-controller onto kind cluster #10
  • ci(ws): run make test-e2e on GitHub Actions #11
• Translate the current CRD spec
  • separate PR, I'd prefer to merge this scaffold separately from that, but up to you ofc
  • feat(ws): add Workspace and WorkspaceKind CRD scaffolds #6
• Declare gha perms/scopes, minimum privilege, because we can

maybe something else from https://docs.google.com/document/d/1SiWLah-U07hAc47sSsoI8-NkbkLnHl1YVzxw193QUKE/edit#heading=h.naudedl8te2q

[thesuperzapper]

@jiridanek I have made a new branch, which we can develop in (rather than main), please make your PR into: https://github.com/kubeflow/notebooks/tree/notebooks-v2

[jiridanek]

there happens to be a cve against this protobuf version; I guess we can fix it with dependabot or something like that

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: thesuperzapper

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [thesuperzapper]

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

[thesuperzapper]

/lgtm