Function app worker runtime check should be case-insensitive

[Grimeh]

The pre-deploy check for mismatching FUNCTIONS_WORKER_RUNTIME values between the remote and local config is case sensitive, blocking deploy even if the worker runtimes only differ by case.
Eg. The remote runtime "DOTNET-ISOLATED" for function app "FoobarApp" does not match your local runtime "dotnet-isolated"..

Our remote runtime was set to DOTNET-ISOLATED which blocked us from deploying from VS Code. Seeing as either value is valid, I believe the comparison (see below) should be case-insensitive.

vscode-azurefunctions/src/commands/deploy/verifyAppSettings.ts

Line 110 in 4be4981

if (localVersion !== FuncVersion.v1 && isKnownWorkerRuntime(azureWorkerRuntime) && isKnownWorkerRuntime(localWorkerRuntime) && azureWorkerRuntime !== localWorkerRuntime) {

Failing that, I suggest promptToUpdateDotnetRuntime be made case-aware. This would allow users to deploy and update the remote runtime to the lower-case dotnet-runtime.

vscode-azurefunctions/src/vsCodeConfig/settings.ts

Lines 121 to 124 in 4be4981

	export function promptToUpdateDotnetRuntime(azureRuntime: string | undefined, localRuntime: string | undefined): boolean {
	return azureRuntime === 'dotnet' && localRuntime === 'dotnet-isolated' ||
	azureRuntime === 'dotnet-isolated' && localRuntime === 'dotnet'
	}

Sidenote: FUNCTIONS_WORKER_RUNTIME in local.settings.json seems to be ignored even when the file exists; tryGetFunctionsWorkerRuntimeForProject derives the value completely independently. Is this intentional?