feat(Iconography): Highlight naming difference for pipeline status

What does this MR do?

Mention that icon prefixed with status_ are strictly limited to pipeline status.

Otherwise a future designer could be confused that they are allowed to icons status- but not prefixed with status_. For example, they may want to convey status at a larger size than 12x12 but missed the fact that status_ is reserved for pipeline status.

A better solution might be to rename the pipeline status but out of scope for this MR.

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.
• Maintainer review follows the Pajamas UX maintainer review checklist.

Links