Support displaying different resource properties

[James Newton-King (JamesNK)]

Description

Telemetry is sent with a resource and a resource has attributes. The first time the dashboard sees a resource it caches it using the name and instance id as the key.

Usually, the attributes on a resource are static. However, it is possible for telemetry to be sent with a resource with the same key but different attributes. When the telemetry is viewed in the UI we want those resource attributes to be displayed, not the initial cached attributes.

This PR:

• Adds OtlpApplicationView. It has a collection of properties
• Caches OtlpApplicationView on OtlpApplication. The key is the properties. This allows views to be shared by telemetry.
• Changes telemetry to refer to the app view instead of app, allowing for the correct properties to be displayed in the UI.
• Tests

Fixes #5126

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

[James Newton-King (JamesNK)]

cc Sam Spencer (@samsp-msft)

[James Newton-King (JamesNK)]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[James Newton-King (JamesNK)]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).