Add the AgenticIdentityFramework callout component

[aatuvai]

This PR adds a new AgenticIdentityFramework callout component according to the Figma design, used to visualize the relationship of a page in the broader Agentic Identity Framework. Aligns with #631 , which is used together with the added component to point users to the Agentic Identity Framework landing page.

Using the component in the .mdx pages:

<AgenticIdentityFramework 
  name="Workload Identity" // the name of the feature which belongs in the framework
  activeCategoryId="identity-for-long-running-agents" // allowed ids found in the component definition
  href="../../../agentic-identity-framework"  // relative path to the landing page
/>

Changes:

• Add src/components/AgenticIdentity
• Add more icons to be used with the Icon component by naming them in src/components/Icon/icons.ts
• Add a new icon src/components/Icon/svg/calendar-check.svg
• Add a new CSS variable --color-background-depth-3

Preview: https://aatuvai-2026-04-27-aif-bottom-callout.d2mrezcly5gcqm.amplifyapp.com/docs/machine-workload-identity/workload-identity/introduction/

[github-actions]

Amplify deployment status

Branch	Commit	Job ID	Status	Preview	Updated (UTC)
aatuvai/2026-04-27-aif-bottom-callout	f699eaa	3	✅SUCCEED	aatuvai-2026-04-27-aif-bottom-callout	2026-04-28 09:40:39

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f699eaaae5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Restore 18.x to an official content branch

The 18.x entry now points to a personal fork/feature branch, and scripts/update_submodules.sh uses these exact branch/repo_path values in CI to fetch docs archives. This means production/CI builds can ingest non-release content (or fail once that fork branch is deleted), and it already violates the repository’s own scripts/validate-docs-config.sh branch policy for merge-group builds.

Useful? React with 👍 / 👎.

[aatuvai]

Converting to draft as the design has some additional changes to come.