Refactor templates into single template groups that allow you select TFM and aspire version

[DamianEdwards]

Description

This merges each template group into a single template that lets you select TFM and Aspire version.

Also addresses some outstanding content and dependency version issues.

Contributes to #6076

Some screenshots of this working in VS locally when I install the new template:

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue: Update template docs for 9.0 GA changes docs-aspire#1869
  • No

Microsoft Reviewers: Open in CodeFlow

[eerhardt]

My understanding is that Microsoft.Extensions.Http.Resilience is on a "tip support" policy. Meaning that only the latest version is supported. (I think there maybe a nuance here where the 8.0 version is LTS, but I can't seem to find the public policy.)

Given the above, I think we should always be referencing the current/latest version of Microsoft.Extensions.Http.Resilience from our templates regardless of TFM chosen. Even if you are targeting net8.0, we would bring in the 9.0 version of Microsoft.Extensions.Http.Resilience.

See also: Use 8.0 era dependencies for non net9.0 TFMs (dotnet/extensions#5470)

cc @joperezr

[DamianEdwards]

Shouldn't our repo be using the 9.x version then too? Currently it's using the 8.x version.

[eerhardt]

Yes. That's part of this as well.

[DamianEdwards]

Should I hold off on a change here until we get consensus?

[joperezr]

I think there is an agreement here. As @eerhardt points out, we want to use the tip of this package both in net8 and net9. There is still the PR that he pointed out above which hasn't been merged but will be merged before 9.0 ships.

[phenning]

SO yea, ignore my comments about missing icons and ide.host.json files - you just need to add AspireVersion to the ide.host.jsons

[DamianEdwards]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[phenning]

one typo, one suggestion

[phenning]

Good from an authoring metadata standpoint

[DamianEdwards]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).