aspire doctor reports "dotnet dev-certs https --trust" even when using non .NET apphost

[davidfowl]

We need to change how this check works and we need an alternative to dotnet dev-certs clear for the non .NET apphosts.

.NET SDK
  ⚠  HTTPS development certificate is not trusted
        Certificate ECE50CB8933D646730D45A466C9C3EE1C36EFA63 exists in the personal store but was not found in the trusted root store.
        Run: dotnet dev-certs https --trust
        See: https://aka.ms/aspire-prerequisites#dev-certs

[danegsta]

@davidfowl how do you feel about an aspire doctor fix sub-command?

I'm thinking something along the lines of:

aspire doctor fix certificates checks certificate state and applies fixes (trust if not trusted, clean and trust if multiple versions are present, etc.)
aspire doctor fix certificates clean would always clean certificates
aspire doctor fix certificates trust would always clean and trust certificates (effectively the command that's run if aspire doctor fix certificates finds an issue)

And just for future compatibility if we end up with other issues we can fix ourselves:
aspire doctor fix --all evaluates and fixes all issues that can be fixed

I'd update all our messages to tell the user to run the appropriate aspire doctor fix command(s) instead of dotnet dev-certs https.