Reassess Knative vs. non-knative cluster experience

Problem

The functionality and configuration for AutoDevOps and Serverless is scattered. There are separate user journeys but its all mixed together within the UI.

For example, on the Kubernetes page we include a Base domain field, as well as a Knative domain field. We also are utilizing Cert Manager as an application for managing SSL Certs, but for Knative we are implementing a separate experience that utilizes GitLab Pages functionality. We've also added GKE Cloud Run as an "alternative" to Knative.

With &1920 (closed), these experiences are splitting further apart but we haven't looked deeply enough into how that affects the interface.

Proposal

Review the user journeys for different types of users and establish an interface that guides the user through what they are trying to accomplish.