Extensions could not be loaded/listeners could not be started when the language worker start is retried

On a recent ICM we had the situation that with worker indexing enabled, the language worker process (python on that specific case) timed out and failed to start several times.

On that situation the JobHost started without finding any job functions:

`No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).`

After a new retry, the host created the language worker channel, it started the python language worker successfully, the host could process the functions metadata with fallback to host indexing and found the functions. However it didn't load the extensions and didn't start the listeners until a manual restart.

#### Investigative information
Example ICM: 399162883
Host Version: 4.21.1.1
Python worker version: 4.14
Python version: 3.9.16

Start by investigating the language worker retry and host-indexing path described in the issue, using the reported Azure Functions, Python worker, and Python versions as context. Done means that after a worker start retry, the host loads the required extensions and starts listeners without requiring a manual restart.

Written by the indexing model from the issue text.