Fixes #12971.

When running wrangler types with multiple -c config flags, secondary workers that have named environments which override the worker name (e.g. name: "do-worker" with env.staging.name: "do-worker-staging") were not being resolved correctly. Any service binding or Durable Object binding in the primary worker that referenced the environment-qualified name (e.g. do-worker-staging) would fall back to an unresolved comment type like:

DurableObjectNamespace /* MyDurableObject from do-worker-staging */
// instead of:
DurableObjectNamespace<import("../secondary/index").MyDurableObject>

This produced ugly union types in the generated Env interface since both the top-level and env-specific bindings could be for different resolved/unresolved types.

Root cause: The secondaryEntries map (which maps worker names to their entry file paths) was only populated with the top-level worker name from each secondary config. When a binding referenced an env-qualified name like do-worker-staging, the lookup missed and fell back to the comment-style unresolved type.

Fix: After registering the top-level name for a secondary config, also read the raw config to iterate over all named environments, load the config for each env, and register the env-specific effective name pointing to the same source entry file.

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: this is a bug fix with no API surface changes