Allow resource properties to be marked as secret

[drewnoakes]

Fixes #5065
Fixes #5377

This change allows selected resource properties in the details view to support masking, and show as masked by default. This behaviour exists today for all environment variables, and has so-far not been available for resource properties.

The resource service specifies which properties may be "sensitive", and the UI shows them masked.

Currently, the app host hides container/executable command line arguments, but it can be amended to include other properties too. Other resource services (like ACA's) can customise this logic to their needs as well.

As part of this change, we create interface IPropertyGridItem that view models must implement to be bound to the PropertyGrid component. This allows the component to work directly with the items, rather than calling back to the component's user via parameters for callback logic that largely do the same thing.

We also avoid having the ResourceDetails code create copies of ResourcePropertyViewModel objects for binding the UI. This copying won't work with the new IPropertyGridItem as the PropertyGrid requires these to be the same mutable object over time. Removing this fixed the inability to unmask resource property values.

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

[davidfowl]

@drewnoakes This is close to being done right?

[drewnoakes]

It's close, but blocked on the (minor) bug mentioned above. The cause seems to be a UI update loop that prevents the popup from opening. I haven't made time to investigate yet, given other priorities, but will come back to it soon.

[drewnoakes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[drewnoakes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[drewnoakes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[drewnoakes]

@JamesNK please re-review and both @davidfowl and I are waiting to build on this for other work (e.g. #4974).