Improve extension startup error discoverability/logging

The generated code from [this code generation template](https://github.com/Azure/azure-functions-dotnet-worker/blob/bf563c49c2f2ab20f6c2d5a56ae9915e87f2d2c6/sdk/Sdk.Generators/ExtensionStartupRunnerGenerator.cs#L214) is reporting the exception in the error stream but not passing it to the application (in this case the Azure Function) error handler. This caused me to waste few days chasing an issue where my function's failed to startup in the cloud. I couldn't find the issue until I downloaded the source code to my local machine and referenced the code directly in my solution to be able to debug locally and find what caused the failures.

This must remove the try/catch to allow developers more flexibility and control over their code.

Start with sdk/Sdk.Generators/ExtensionStartupRunnerGenerator.cs at the linked code around line 214 and inspect how generated extension-startup exceptions are handled. Verify whether the exception reaches the Azure Function application's error handler instead of only the error stream; done means startup failures remain discoverable through the application handler without the current try/catch behavior.

Written by the indexing model from the issue text.