Insert Resource should first check for Visual Studio credentials

Similar to our Right click deploy feature, We want to eliminate our reliance on the Azure CLI as a user is using the Bicep extension. This helps in plenty of remote scenarios.

So we will check for visual studio first and prompt them to download the Azure account extension and sign in using it.

We can reuse the same popup when they try this command and we find no credentials.

Start at the Insert Resource command and compare its credential lookup with the existing Right click deploy feature. Trace the no-credentials popup and the Azure CLI fallback described in the issue. Done means Insert Resource checks Visual Studio credentials first, reuses the existing popup when none are found, and no longer relies on the Azure CLI in this scenario.

Written by the indexing model from the issue text.