feat: bind a durable object by environment

[threepointone]

For durable objects, instead of just { name, class_name, script_name}, this lets you bind by environment as well, like so { name, class_name, script_name, environment }.

Fixes #996

[changeset-bot]

🦋 Changeset detected

Latest commit: d37613b

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/2331924480/npm-package-wrangler-1019

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

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

Or you can use npx with this latest build directly:

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

[petebacondarwin]

In the original issue you say:

This should probably only work with service environments (with legacy, you'd add - to the script_name)

I don't think this has been taken into account here, right? Should we add a check for legacy env?

[threepointone]

So we have docs that show you how to bind to workers with "legacy" environments https://developers.cloudflare.com/workers/learning/using-durable-objects/#configuring-durable-object-bindings. There's maybe something we can do here where we specify legacy: true and automatically add -<env name> to the worker name, but I dunno how I feel about that just yet. I figured we'd land this first and work on that later when it's asked for.