fix(wrangler): avoid path collisions between performance and Performance polyfills

[IgorMinar]

It turns out that ESBuild paths are case insensitive, which can result in path collisions between polyfills for globalThis.performance and globalThis.Performance.

This change ensures that we encode all global names to lowercase and decode them appropriately.

The version of unenv used at HEAD currently doesn't suffer from this path collision, but if not fixed the change introduced in https://github.com/unjs/unenv/pull/257/files would result in Node.js API coverage regressions. This change prevents those regressions from happening.

What this PR solves / how to test

Fixes #[insert GH or internal issue number(s)].

Author has addressed the following

• Tests
  • TODO (before merge)
  • Included
  • Not necessary because:
• E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required / Maybe required
  • Not required because:
• Changeset (Changeset guidelines)
  • TODO (before merge)
  • Included
  • Not necessary because:
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Not necessary because:

[changeset-bot]

🦋 Changeset detected

Latest commit: 6effdba

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
wrangler	Patch
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9498249323/npm-package-wrangler-6025

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6025/npm-package-wrangler-6025

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9498249323/npm-package-wrangler-6025 dev path/to/script.js

Additional artifacts:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9498249323/npm-package-create-cloudflare-6025 --no-auto-update

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9498249323/npm-package-cloudflare-kv-asset-handler-6025

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9498249323/npm-package-miniflare-6025

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9498249323/npm-package-cloudflare-pages-shared-6025

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9498249323/npm-package-cloudflare-vitest-pool-workers-6025

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.60.2 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20240605.0
workerd	1.20240605.0	1.20240605.0
workerd --version	1.20240605.0	2024-06-05

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[petebacondarwin]

This fix looks fine to land.
But I think that actually this is not the best approach for these virtual files.
Rather than using virtual fake paths (which in extreme cases could collide with real paths), I think the correct approach is to use esbuild namespaces here to filter these resolves to loaders.
We might still need to encode/decode upper case letters from globals to distinguish between globals that only differ in case, but we could avoid having to use getBasePath() and the concern of path collision.

[petebacondarwin]

It needs a changeset before I merge...

[holopin-bot]

Congratulations @IgorMinar, you just earned a holobyte! Here it is: https://holopin.io/holobyte/clxd6dfbz31420cmgnkzuoc3x

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!