Using an incorrect storage key in a blob trigger function puts the entire function app in bad state.

Repro steps:
1. Create a v3 function app
2. Create a blob trigger function
3. Use a new connections string which has the correct format, but has an expired key.

Result:
The function runtime is unable to start and throws the following error.

Expected:
The function app should keep running normally, The function using the bad connections string should be in error statae

No source file, test, or entry point is named. Reproduce the v3 Azure Functions app with a blob trigger and an expired storage key, then inspect the runtime startup error and compare the host-wide failure with the expected per-function error state. Done means the app remains running while only the function using the invalid connection is in error.

Written by the indexing model from the issue text.