Worker may not restart when crashing in multi-language environment

The [code here](https://github.com/Azure/azure-functions-host/blob/20e517f0//src/WebJobs.Script/Workers/Rpc/FunctionRegistration/RpcFunctionInvocationDispatcher.cs#L475-L485) checks whether the `FUNCTIONS_WORKER_RUNTIME` matches that of the worker that just crashed. In Functions-hosted scenarios, this works becuase there is only one worker language. However, in Logic Apps scenarios, the `FUNCTIONS_WORKER_RUNTIME` means very little and should not even be checked here.

The problem is this can cause a crashed worker to never restart. The host doesn't know this, so it continues accepting invocations and they all eventually timeout forever until the host is restarted.

Start in src/WebJobs.Script/Workers/Rpc/FunctionRegistration/RpcFunctionInvocationDispatcher.cs around lines 475-485 and trace the worker crash handling flow. Verify the behavior for Logic Apps multi-language scenarios and ensure a crashed worker can restart instead of leaving later invocations timing out indefinitely.

Written by the indexing model from the issue text.