Bind to VPC Services by name rather than service_id

[sodabrew]

Describe the solution

In commit 555a6da / PR #10647, VPC Services bindings were added by giving a binding name visible to the worker script and a service_id copied from the VPC Services page. The config stanza is:

"vpc_services": [
  { "binding": "NAME", "service_id": "a-b-c-1-2" }
]

This ticket is a request to allow { "binding": "NAME", "service": "name" } and let wrangler look up the service_id as an internal detail.

[sodabrew]

cc @efalcao @petebacondarwin

[sodabrew]

PR #13387 implements this suggestion for VPC Services.
PR #13388 extends it to other bindings.

[sodabrew]

Network identifiers don't look too terrible, but tunnel identifiers are UUIDs like service identifiers. My PRs were marked draft until this conversation is resolved. May we begin the discussion at the least?

https://blog.cloudflare.com/mesh/#integrated-with-the-developer-platform-with-workers-vpc

"vpc_networks": [
  { "binding": "MESH", "network_id": "cf1:network", "remote": true },
  { "binding": "AWS_VPC", "tunnel_id": "350fd307-...", "remote": true }
]