Setting ENV variables via local.settings.json triggers existing M1 error

I just found a bug/edge case, that in theory it was ironed out.

It turns out that when I adding an `env` variable to `local.settings.json`, that contains a `list` or a `dict` as value, the already M1 tracked bug resurfaces

```
[2023-10-19T13:26:57.042Z] Failed to initialize worker provider for: /opt/homebrew/Cellar/azure-functions-core-tools@4/4.0.5413/workers/python
[2023-10-19T13:26:57.042Z] Microsoft.Azure.WebJobs.Script: Architecture Arm64 is not supported for language python.
```

Just by adding
```json
{
"IsEncrypted": false,
"Values": {
"FUNCTIONS_WORKER_RUNTIME": "node",
"FUNCTIONS_EXTENSION_VERSION": "~4",
"AzureWebJobsFeatureFlags": "EnableWorkerIndexing",
"AzureWebJobsStorage": "UseDevelopmentStorage=true",
"AzureWebJobsDashboard": "UseDevelopmentStorage=true",
"AzureTaskHub": "parallelTaskProcessor",
"list": ["one"],
"dict": {"i": {"like": "turtles"}}
},
"Host": {
"LocalHttpPort": 7072,
"CORS": "*",
"CORSCredentials": false
}
}
```

Perhaps those types of values are not supported at all, but it is strange that this issue appears for that

Start by reproducing the startup failure with the provided local.settings.json, especially the list and dict values under Values, and compare it with scalar-only settings. Trace the local settings loading and worker initialization entry points to determine whether these value types are supported; done means the behavior is corrected or the supported-value limitation is clearly established.

Written by the indexing model from the issue text.