Improve Listener retry behavior

We should also investigate ways to mitigate issues as happened in ICM #86612384. In that case, it appears that for a very long time (10+ hours) function listeners were unable to start due to failures to connect to storage. The host was up and running and the listeners were stuck in a restart/retry loop for a very long time. Once the user noticed and restarted the app, things started working immediately, indicating a platform issue with DNS resolution or something, rather than a connection string issue or storage outtage. We need to find a way to recover from cases like this automatically.

The issue does not name any files, tests, or entry points. Start by tracing function listener startup and its storage-connection retry loop, using the described DNS or storage connection failure as the scenario. Done means listeners recover automatically without requiring an app restart.

Written by the indexing model from the issue text.