Clarify template installation guidance: CLI-first flow with .NET fallback

[Copilot]

The templates page implied dotnet new install applied broadly and referenced the obsolete “Aspire workload,” which caused confusion about the intended setup path. This update makes aspire new the primary flow and scopes dotnet new install explicitly to .NET template installation fallback.

• Primary path: Aspire CLI

  • Replaced the top-level install section with a CLI-first section: “Install templates with Aspire CLI (recommended)”.
  • Clarified that aspire new handles template installation automatically.

• .NET-specific fallback

  • Added a clearly scoped subsection: “Install the .NET project templates (dotnet fallback)”.
  • Kept dotnet new install Aspire.ProjectTemplates guidance and version pinning example, but explicitly framed it as direct dotnet installation.

• Terminology cleanup

  • Removed the outdated “Aspire workload” phrasing from this page section.

# Recommended
aspire new aspire-starter

# .NET fallback
dotnet new install Aspire.ProjectTemplates
dotnet new install Aspire.ProjectTemplates::13.1.0

[Copilot]

Pull request overview

This PR updates the “Aspire SDK templates” getting-started documentation to make the Aspire CLI the primary workflow for using templates, while clearly scoping dotnet new install to a .NET-specific fallback path.

Changes:

• Replaces the top-level “install templates” guidance with a CLI-first aspire new flow.
• Adds a clearly labeled “dotnet fallback” subsection for installing templates into dotnet.
• Removes the outdated “Aspire workload” phrasing from this page section.

---

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