Create unity among all necessary steps to use Auto DevOps

Problem

Auto DevOps settings currently exist within CI/CD settings. From this view, it is unclear to users what is needed to use Auto DevOps. This problem was validated in our user research: ux-research#67 (closed). Most users were unsure what a domain was for and all users were not aware they needed a cluster.

Problem statement

Users should have a clear understanding of what is necessary in order to fully configure Auto DevOps.

Prerequisites

• https://gitlab.com/gitlab-org/gitlab-ce/issues/47156

Solution

As a first step towards solving the problem, we can create a central area for users to navigate to that includes all configuration necessary for using Auto DevOps.

This currently consists of:

• Showing whether the project is defaulting to the Auto DevOps pipeline with a link to edit it
• Showing whether the user has a cluster configured with a link to edit it
• Showing whether a domain has been added (to be added directly to cluster flow in [ADD ISSUE LINK])
• Showing whether a deploy token has been created (contingent upon us doing it automatically https://gitlab.com/gitlab-org/gitlab-ce/issues/46075)
• Showing whether the user has a domain strategy configured

[ADD MOCKUPS]

Further improvements

• Improve cluster creation flow [ISSUE LINK]
• Create Auto DevOps Wizard [ISSUE LINK]