feat(FeatMgmt): Update badge and popover of feature versions

What does this MR do?

Updates to Pajamas on how we should communicate feature version badges on Experiment and Beta features.

• Adding more help content to the popover
• Adding small variants when space is tight
• To avoid a hard distinction between the label and the feature badge, a neutral colour should be used within the badge, a neutral colour would also be less overwhelming when multiple info badges appear in the same context.

Screenshots or screen recordings

Copy change and image changes based on discussions from this issue

Before	After

How to set up and validate locally

On the left sidebar:

• Find the Usability and interaction option
• InUsability and interaction find Feature management option
• Scroll down to Highlighting feature versions

Does this MR meet the acceptance criteria?

• The MR title and commit messages meet the Pajamas commit conventions.
• The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”.
  • For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
• Relevant label(s) are applied to the MR.
• The MR is added to a milestone.
• If creating a new component page from scratch, it follows the page template structure.
• Content follows the Pajamas voice and tone guidelines, falling back on the GitLab Documentation Style Guide when needed.
• Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter.
• If embedding a Figma file, it follows the Figma embed guide.
• Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.

Links

Related to #1580 (closed)