Lacking all zones permission should be an INFO not a WARNING

[GregBrimble]

What versions & operating system are you using?

wrangler v4.39.0

Please provide a link to a minimal reproduction

No response

Describe the Bug

▲ [WARNING] The current authentication token does not have 'All Zones' permissions.
  Falling back to using the zone-based API endpoint to update each route individually.
  Note that there is no access to routes associated with zones that the API token does not have permission for.
  Existing routes for this Worker in such zones will not be deleted.

The user shouldn't change anything here. Having an API token scoped to a particular zone is completely valid behavior, and it sounds like Wrangler can handle that just fine. We shouldn't present this as a WARNING to users. Instead, it should be an INFO, if anything.

Please provide any relevant error logs

No response

[penalosa]

Existing routes for this Worker in such zones will not be deleted.

This feels like the potentially dangerous warning bit. We don't have any way to tell if the Worker is accessible on other routes that we can't tell you about

[petebacondarwin]

It is a shame that we cannot tell if this Worker has no routes to other zones, even if we are not allowed to know what they are.
If that were the case then we could leave this as a warning but only show it if the number of zones is greater than one.

Can we implement that in the backend instead? E.g. an API call that is scoped to single zone permission that returns "number of zones for this Worker"?

[petebacondarwin]

But I guess that at least showing this message and changing it to INFO is a reasonable intermediate step.