Azure Functions when run locally with `defaultWatchEnabled=true` expects IDE connection

When I'm using a Azure Function with apphost, and have `defaultWatchEnabled=true` in `~/.aspire/globalsettings.json` then running aspire locally causes the function to fail with this:

`stderr Timeout of 120 seconds exceeded waiting for the IDE to start a run session; you can set the DCP_IDE_REQUEST_TIMEOUT_SECONDS environment variable to override this timeout (in seconds) {"Executable": "/functions-bnxfrcgk", "Reconciliation": 596, "error": "Put \"https://localhost:64909/run_session?api-version=2024-04-23\": context deadline exceeded"}`

If I disable the setting then it works fine. I'm not sure what the correct behavior here would be. But we should at least tell the user that we are waiting for IDE because of the dotnet-watch setting.