[FEATURE] Deploy backend as a k8s workload

[andyatmiami]

Motivation

We are still in the early infancy of the Kubeflow Notebooks 2.0 timeline, but plan/hope to greatly accelerate its development and progress in the coming days/weeks/months.

Currently, based on code available in the notebooks-v2 branch, the backend components is only able to be run locally on a developer's workstation. We want to be able to (easily) deploy backend component to a kubernetes cluster in order to:

• realize the desired architecture
• improve the end-to-end testing experience
• allow for more realistic demos

High Level Design/Mock-ups

n/a

Acceptance Criteria

• backend component can be deployed as a workload to kubernetes
• Workload is stable when running in a cluster
• All endpoints implemented in backend are functional and reflect the state as it exists in the cluster

Work Items

• Properly containerize backend component #323
• Define k8s workload manifest for backend component #324

[andyatmiami]

/area v2
/area backend