"Install the Aspire Templates" section should be clear it's referring specifically to `dotnet`

[afscrome]

https://aspire.dev/get-started/aspire-sdk-templates/?dev-environment=aspire-cli#install-the-aspire-templates

This "Install the Aspire Templates" section should be clear that it's specifically referring to .Net. It also refers tot hte "Aspire workload" which isn't a thing any more. Although maybe now aspire new is a thing, it's better to document just the aspire new path, or at the very least move the dotnet specific parts to the end of the page?

I think this could have contributed to some of the confusion on microsoft/aspire#17448

[IEvangelist]

Triage → @Copilot

Page: https://aspire.dev/get-started/aspire-sdk-templates/ → src/frontend/src/content/docs/get-started/aspire-sdk-templates.mdx

Scope

1. Make the "Install the Aspire Templates" section explicit that it covers the .NET templates installed via dotnet new install Aspire.ProjectTemplates. The current copy reads like it applies to all language SDKs.
2. Remove the phrase "Aspire workload" — workloads are no longer used; templates ship as a NuGet package.
3. Prefer/lead with the aspire new flow where the CLI handles template installation transparently; keep the dotnet new install path as a secondary/.NET-specific section.

Acceptance

• Section header clarifies .NET scope (e.g. "Install the .NET project templates").
• No remaining references to "Aspire workload" in this page.
• aspire new is the primary path; dotnet new install is documented as the .NET fallback.
• No unrelated content changes.