Unhandled exceptions cause hang instead of 500 error from HTTP triggers after core tools version update.

I am finding that unhandled exceptions thrown from a HTTP triggers (ASP.NET Core extension) produce different behavior between versions 4.0.5611 and 4.0.5801(latest) of azure-functions-core-tools.

Running with `func start` for version 4.0.5611, unhandled exceptions return 500 errors.
Running with `func start` for version 4.0.5801, unhandled exceptions return no response (until an eventual timeout).
Expected result: unhandled exceptions return 500 errors in both versions.

Here is a test project and more detailed reproduction steps: https://github.com/zkingston-polly/isolated-func-500-handling

OS: Windows

Start with the linked reproduction project and run `func start` on Windows using azure-functions-core-tools 4.0.5611 and 4.0.5801. Compare HTTP-trigger behavior for unhandled exceptions; done means both versions return HTTP 500 responses instead of hanging until timeout.

Written by the indexing model from the issue text.