Fixing unintended formatting changes

[joperezr]

Description

When making the workload changes, I ran the xml formatter on the SDK.targets file to format tabs/spaces and indentation correctly, but it looks like that made some formatting changes that introduced bugs like adding newlines to property values, which would then break conditions when doing string comparisons. Thanks a lot @eerhardt for debugging and finding this out. The changes in this PR revert all the formatting changes made in that PR, which means the net difference since 8.1 will be the addition of the new target.

Fixes #5436

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:
  • No

Microsoft Reviewers: Open in CodeFlow

[joperezr]

After applying the changes in this PR locally, I can see that the issue is resolved:

[eerhardt]

LGTM. Thanks for fixing this!

[joperezr]

/backport to release/8.2

[github-actions]

Started backporting to release/8.2: https://github.com/dotnet/aspire/actions/runs/10601707713

[v-elenafeng]

@joperezr Is this ready to be merged? We're still experiencing the issue with 9.0 P4.