Clarify what wildcard environment scopes are in the CI/CD Variables settings.

Problem to solve

Create a UX solution to clarify what "Create wildcard:" means in the Environment Scope dropdown when adding or updating a variable in the CI/CD Variables settings.

From this discussion (#5313 (comment 385278944)):

It might add some clarity to add a tooltip or link defining what a wildcard environment scope is in this UI.

Proposal

Address the possibility that a user might not know what a wildcard environment scope is in the context of the Variables table UI.

UX Proposal

• On Project settings > CI/CD > Variables, add a help icon (?) next to the label Environment scope.
• The help icon (?) should link to the documentation page for scoping environments with spec
  • https://docs.gitlab.com/ee/ci/environments/#scoping-environments-with-specs

Prototype

Permissions and Security

• Add expected impact to members with no access (0)
• Add expected impact to Guest (10) members
• Add expected impact to Reporter (20) members
• Add expected impact to Developer (30) members
• Add expected impact to Maintainer (40) members
• Add expected impact to Owner (50) members

Links / references

• https://design.gitlab.com/usability/helping-users
• https://docs.gitlab.com/ee/ci/environments/#scoping-environments-with-specs