**Is your feature request related to a problem?

Once again, trusted signing has been rebranded, this time into artifact signing. See announcement [here].(https://techcommunity.microsoft.com/blog/microsoft-security-blog/simplifying-code-signing-for-windows-apps-artifact-signing-ga/4482789?previewMessage=true)

Given that this coincides with the GA announcement, I would expect we will keep this name moving forward. Ideally, we could also match the trusted signing provider under the artifact signing branding, to avoid confusion. Before I submit a PR, I would like to understand what's the support guidance for customers using the current trusted signing provider? I understand that this tool appears as prerelease, but I'm very open to suggestions and guidance on how to proceed with the name change.

cc: @ianjmcm