Text guidance for blank state

We don't have consistent text in our blank state pages in the UI. We need to create guidance and apply it.

Related to: gitlab-org/gitlab#339525[Deleted-many-items.png] (comment 807219530)

If you look at the following examples, the most effective ones have a call to action.

Should there be different text, based on the type of page? For example, does it make sense to have a call to action on a search or filter page that shows no results?

Current guidance

I found this info in Pajamas:

• https://design.gitlab.com/regions/empty-states
• https://design.gitlab.com/regions/empty-states#blank-content

And there is an empty state template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Empty%20state

It does define different types of blank state pages:

• Blank page with a call to action
• Configuration required
• Higher tier required
• Empty search results

We should recommend text for each.

Examples of empty state pages

The following are just random examples from the UI.

Package Registry

https://gitlab.com/sselhorn/test-project/-/packages

Pipelines

https://gitlab.com/gitlab-org/gitlab/-/pipelines?page=1&scope=finished&username=gdoyle

Merge requests

https://gitlab.com/dashboard/merge_requests?scope=all&state=opened&assignee_username=hmjang1

Issues

https://gitlab.com/gitlab-org/gitlab/-/issues?search=adkfhasidhf&sort=created_date&state=opened

Container Registry

Infrastructure Registry

Monitor > Metrics

Monitor > Tracing

Monitor > Incidents

Security & Compliance > Security Dashboard

Commit search

https://gitlab.com/gitlab-org/gitlab/-/commits/master?search=gdgdfg

Repository > Locked files

Issues > Milestones

https://gitlab.com/sselhorn/test-project/-/milestones

Issues > Requirements

CI/CD > Schedules

CI/CD > Test cases

Deployments > Feature flags

Infrastructure > Serverless platform