docs(contribute): Move component lifecycle up

What does this MR do?

This MR proposes moving the component lifecycle information from docs to be displayed at a higher level, in the Pajamas website. Initially discussed on #505 (closed), this proposal aims to provide designers not only with a clear guidance about the steps to complete the Create, Build, and Style Pajamas process, but also to facilitate the discoverability of the process. When designers have to start contributing to Pajamas, there's usually a lot of questions related to the process, where to start, or what is the best approach to contribute. My assumption is that the existing information is not accessible enough. Some examples:

• #274 (comment 313014678)
• gitlab-org&4246 (comment 399546142)
• https://www.youtube.com/watch?v=xWuebXViqG8

The docs page is not removed, but a link to the new SSOT is added.

The component lifecycle is replaced to display an svg image (mermaid graph did not work with Pajamas).

Does this MR meet the acceptance criteria?

• The MR title and commit message meet the Pajamas commit conventions
• Add a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Include MR scope that reflects the purpose of the change in the description
  • For example, if this MR is focused on usage guidelines, addressing accessibility challenges could be added separately with a different MR
• If creating a new page on Pajamas from scratch, follow the page template structure
• Follow the Pajamas Voice & Tone Guidelines and GitLab Documentation Style Guide
• Link components to and from other related components and patterns on the .md file, where helpful
• Assign it to a reviewer. All GitLab designers are reviewers, but you can also assign it directly to a maintainer or trainee maintainer
• Apply the correct component label(s)
• Select a milestone or due date

Links

Closes #699 (closed)