Update OTEL in templates

[danmoseley]

Description

Update to latest otel in templates.

Fixes #9060

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 (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[danmoseley]

@radical I think what we're seeing here is that the templates are being restored by the tests using our mirror feed, when they should be able to get to nuget.org. Not a priority to fix though -- I'll mirror.

[danmoseley]

https://dev.azure.com/dnceng/internal/_build/results?buildId=2700533&view=results

[DamianEdwards]

Note that the OTel packages don't always share the same versions, so you need to verify the specific latest version for each one.

[DamianEdwards]

@danmoseley did you mirror the OTel packages that were published to nuget yesterday, or does this just need a re-run?

[danmoseley]

mirroring completed - rerunning