Use SQL input / output template instead

[VasuBhog]

This PR changes the logic for Create Azure Function with SQL Binding. We used to first create an azure function and then have to use the command addSQLBinding to then add it to the specific function file that was created. This resulted in not the best practices of overwriting the function text body.

Now that the SQL Templates are released we should be able to leverage this (Azure/azure-functions-templates#1162). Based on what the user chooses we will create either a SqlInputBinding or SqlOutputBinding.

Current Flow:

1. User uses Create Azure Function with SQL Binding from a selected table.
   a. If user doesn't have a function file go through create flow
2. User chooses a function project folder (if many)
3. Prompt for Function Name (placeholder of table name)
4. Prompt for type of binding
5. Prompt for namespace
6. Issue - SQL Binding Templates shows storage account wizard #18780 if AzureWebJobsStorage in local.settings.json is empty
7. Adds SQL Nuget Reference and adds connections string to local.settings.json file

Function file is created (shown below):

[Charles-Gagnon]

Do we still need this? I thought the template added this for us as well.

[VasuBhog]

No, just checked this. The template does add the NuGet reference.

<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.Sql" Version="0.1.131-preview" />

[VasuBhog]

In regards to the issue in step 6. There is an issue when AzureWebJobsStorage is an empty string as vscode-azurefunctions logic is set up to ask this question for everything except HTTP triggers.
https://github.com/microsoft/vscode-azurefunctions/blob/main/src/debug/validatePreDebug.ts#L123

The current workaround to suppress this set the AzureWebJobsStorage a placeholder value: Enter your Azure Web Jobs storage connection string.