Update workers routes validity

[aaronadamsCA]

Example URL(s)

https://developers.cloudflare.com/workers/configuration/routing/routes/#validity

Actual Behavior

The docs clearly state that a route pattern must include the zone name:

cloudflare-docs/src/content/docs/workers/configuration/routing/routes.mdx

Lines 133 to 135 in b9e1d40

	#### Route patterns must include your zone
	If your zone is `example.com`, then the simplest possible route pattern you can have is `example.com`, which would match `http://example.com/` and `https://example.com/`, and nothing else. As with a URL, there is an implied path of `/` if you do not specify one.

Expected Behavior

Cloudflare for SaaS has long recommended a "*/*" route pattern:

cloudflare-docs/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx

Lines 23 to 28 in b9e1d40

	4. Decide whether you want traffic bound for your SaaS zone (`example.com`) to go to that Worker:
	* If *yes*, set the following values:
	* **Route**: `*/*` (routes everything — including custom hostnames — to the Worker).
	* **Worker**: Select the Worker used for your SaaS application.

This pattern doesn't include the zone name, but it works great! So I'm guessing the workers routes doc is just outdated.

Additional information

No response

[kodster28]

I think related to #5584

[aaronadamsCA]

Definitely related, but we just do this to bind all zone traffic to our worker:

[[routes]]
pattern = "*/*"
zone_name = "example.com"

Whereas #5584 is about the case where you don't want to do that.