cloudflare: remaining dev emulation gaps after #4608

Follow-up to #4608. These gaps in Cloudflare dev emulation (miniflare runner) were found during review and are still open.

Needs changes in env-runner:

• When cloudflare.wrangler is set inline, the wrangler config file is only looked up in the cwd, not rootDir. If the inline env map lacks the selected wranglerEnv, the file's bindings are dropped too. Nitro needs a way to pass an explicit config path together with the inline config.

Nitro side:

• Dev and production resolve named environments differently. Dev applies wranglerEnv to the inline config and the file separately and then merges the results, while the build merges the raw configs first. Inline top-level bindings are visible in dev but not after deploy.
• The /_nitro/tasks/:name dev endpoint runs tasks without context.cloudflare, which the production scheduled handler provides.
• Service bindings to other workers are now removed in dev without a warning, so env.MY_SERVICE is just undefined.

Request forwarding, the request runtime context and the leaked internal bindings were fixed in env-runner 0.2.2 (unjs/env-runner#50).

Opened with AI assistance.

Start by tracing the miniflare runner and env-runner handling for inline Wrangler configuration, rootDir lookup, and named environments. Then inspect the /_nitro/tasks/:name endpoint and the production scheduled handler to compare runtime context and service bindings. Done when the listed dev-versus-production gaps are resolved and the behavior is covered by verification.