fix: work with Cloudflare WARP

[threepointone]

Using wrangler with Cloudflare WARP (https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/) requires using the Cloudflare certificate. This patch simply uses the certificate as NODE_EXTRA_CA_CERTS when we start wrangler.

Test plan:

• Turn on Cloudflare WARP/ Gateway with WARP
• wrangler dev
• Turn on Cloudflare WARP/ Gateway with DoH
• wrangler dev
• Turn off Cloudflare WARP
• wrangler dev

Fixes #953, #850

[changeset-bot]

🦋 Changeset detected

Latest commit: ad1ce22

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

This PR includes changesets to release 1 package

Name	Type
wrangler	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.developers.workers.dev/runs/2307096669/npm-package-wrangler-963

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

npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/963/npm-package-wrangler-963

Or you can use npx with this latest build directly:

npx https://prerelease-registry.developers.workers.dev/runs/2307096669/npm-package-wrangler-963 dev path/to/script.js

[threepointone]

Huh, I'm actually able to reproduce the test failures locally. Investigating.

[threepointone]

Alright, I figured it out. You need to extend env with process.env to pass on all env values. Also caught a bug, where I wasn't including the .pem file in the published package. Fixed both, hopefully CI passes now, and I'll land it.

[petebacondarwin]

Luckily you can get away with using __dirname here because we are not bundling this file with esbuild 😺