Set hosting configuration to enable worker decoupling feature

The below Hosting config will enable the feature in Production. However, in the absence of a deployed worker site extension, no action will occur, and the Host will proceed to search for worker configurations within it.

```FunctionsHostingConfig__WORKERS_AVAILABLE_FOR_DYNAMIC_RESOLUTION="java|node|dotnet-isolated" ```

The plan is to get R2D approval and enable the feature in Production. If there are no errors, deploy a worker site extension with the next Host release -- this will allow Host to look for worker config of a decoupled worker.

Start by reviewing the production hosting configuration and the WORKERS_AVAILABLE_FOR_DYNAMIC_RESOLUTION setting described in the issue. Confirm the R2D approval path and deployment prerequisites, then verify that enabling the setting produces no errors when no worker site extension is deployed. Done means the production configuration is enabled and the follow-up worker site extension is scheduled for the next Host release.

Written by the indexing model from the issue text.