Improve Type/Method/Field links in descriptions in ConfigurationSchemaGenerator

[eerhardt]

When the ConfigurationSchemaGenerator encounters XML docs like

aspire/src/Components/Aspire.Azure.Security.KeyVault/AzureSecurityKeyVaultSettings.cs

Lines 16 to 17 in bc220e3

	/// A <see cref="Uri"/> to the vault on which the client operates. Appears as "DNS Name" in the Azure portal.
	/// If you have a secret <see cref="Uri"/>, use <see cref="KeyVaultSecretIdentifier"/> to parse the <see cref="KeyVaultSecretIdentifier.VaultUri"/> and other information.

It generates a description node like:

aspire/src/Components/Aspire.Azure.Security.KeyVault/ConfigurationSchema.json

Line 119 in cce3914

"description": "A T:System.Uri to the vault on which the client operates. Appears as \"DNS Name\" in the Azure portal.\nIf you have a secret T:System.Uri , use T:Azure.Security.KeyVault.Secrets.KeyVaultSecretIdentifier to parse the P:Azure.Security.KeyVault.Secrets.KeyVaultSecretIdentifier.VaultUri and other information.\nYou should validate that this URI references a valid Key Vault resource. See https://aka.ms/azsdk/blog/vault-uri for details."

We should see if we can do something better here, at least dropping the T: and maybe quoting the type name.

"description": "A 'System.Uri' to the vault on which the client operates

[kiapanahi]

This issue is closed by #1473. I just forgot to mention it as "Closes #1428" in that PR's description.