Docs: capture 13.2 Foundry rename breaking changes and remove legacy AIFoundry references

[Copilot]

Aspire 13.2 renamed the hosting integration from Aspire.Hosting.Azure.AIFoundry to Aspire.Hosting.Foundry, including namespace and related type renames. This update ensures the 13.2 changelog explicitly documents the full migration surface and removes stale legacy identifiers from docs content.

• 13.2 changelog: complete migration mapping

  • Expanded the breaking-changes entry in whats-new/aspire-13-2.mdx with a full rename table (package, namespace, and type renames).
  • Added a concise migration tip covering package reference, using directive, and direct type-reference updates.
  • Updated section naming and intra-page links to match the new transition section title.

• Legacy-name cleanup in docs content

  • Removed remaining legacy AIFoundry/AddAzureAIFoundry mentions under src/frontend/src/content/docs/.
  • Updated Foundry migration examples to use current APIs (AddFoundry, FoundryModel) and current naming guidance.
  • Applied equivalent cleanup in localized 13.2 release notes (ja/whats-new/aspire-13-2.mdx) for consistency.

• Related integration guidance alignment

  • Revised the upgrade note in azure-ai-foundry-host.mdx to describe migration using current Foundry naming without retaining deprecated identifiers.

| Previous 13.1 name                     | 13.2 name                      |
| ---                                     | ---                            |
| Aspire.Hosting.Azure.AIFoundry          | Aspire.Hosting.Foundry         |
| Aspire.Hosting.Azure.AIFoundry (import) | Aspire.Hosting.Foundry (import)|
| AzureAIFoundryResource                  | FoundryResource                |
| AzureAIFoundryExtensions                | FoundryExtensions              |
| AzureAIFoundryDeploymentResource        | FoundryDeploymentResource      |
| AIFoundryModel                          | FoundryModel                   |

[Copilot]

Pull request overview

Updates Aspire documentation to reflect the Aspire 13.2 rename from the legacy Azure AI Foundry hosting surface to the unified Foundry naming, and removes remaining legacy identifiers from examples and guidance.

Changes:

• Expanded Aspire 13.2 breaking-change guidance with a rename/migration table and updated section links/headings.
• Updated older “what’s new” content and examples to use AddFoundry instead of AddAzureAIFoundry.
• Adjusted Azure AI Foundry integration upgrade guidance to prefer current Foundry naming.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.

File	Description
src/frontend/src/content/docs/whats-new/aspire-9-4.mdx	Updates code examples to use AddFoundry naming.
src/frontend/src/content/docs/whats-new/aspire-13-2.mdx	Expands breaking-change migration details and updates section naming/anchors.
src/frontend/src/content/docs/ja/whats-new/aspire-13-2.mdx	Mirrors the 13.2 migration/rename documentation updates for Japanese release notes.
src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx	Updates upgrade note to focus on current Foundry naming guidance.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Adam Ratzman (adamint)]

I found two migration accuracy issues that I think need to be fixed before merge: the 9.4 page now uses an API that did not exist in 9.4, and the 13.2 migration table lists the old package ID as a namespace while omitting the actual AddAzureAIFoundry → AddFoundry step. The rendered English and Japanese anchors/tables work, and the current package and type names otherwise line up with the shipped packages.

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1163. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.

[aspire-repo-bot]

Automated wording suggestions from the forbidden-words check. Apply the suggestions to resolve them.