Update CI Catalog design doc with a single view

What does this MR do and why?

Related to Update Design Doc with new unified catalog (#428183 - closed)

Update CI Catalog design doc with a single global view. Revisit glossary and other minor aspects.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

changed milestone to %16.6

added Category:Pipeline Composition devopsverify documentation featureenhancement grouppipeline authoring sectionci typefeature workflowin dev labels

assigned to @fabiopitino

removed workflowin dev label

@dhershkovitch @ayufan Please review.

requested review from @dhershkovitch and @ayufan

added docs-only label

removed review request for @ayufan

approved this merge request

resolved all threads

marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

enabled an automatic merge when the pipeline for 6daa87a8 succeeds

	1 Warning
	This Merge Request needs to be labelled with Architecture Evolution Blueprint. Please request a reviewer or maintainer to add them.

	2 Messages
	This merge request might require a review from a Coach Engineer.
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Architecture Evolution Review

This merge request might require a review from a Coach Engineer.

Following files, that may require the additional review, have been changed:

• doc/architecture/blueprints/ci_pipeline_components/index.md

Documentation review

The following files require a review from a technical writer:

• doc/architecture/blueprints/ci_pipeline_components/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

merged

mentioned in commit f04ad821

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label