What?

Fixes #53433.
Fixes #52157.

Unfortunately, many wp-env commands don't work without internet due to a function which finds the latest WordPress version, which happens during config parsing. Beyond this function, wp-env start could fail in many cases when it tries to do updates (like downloading sources or pulling docker images).

Why?

Offline mode always has its uses!

How?

1. Create a function which uses dns.resolve( 'WordPress.org' ) to check for internet access. This seems to be a reasonable practice based on my search for how to do this with NodeJS. It's also very fast, which isn't the case when we wait for timeouts in other functions.
2. Cache the latest WordPress version in our cache file, and use it when we have no internet. It's probably possible to code this without needing the cache (we could just reuse the existing docker-compose.yml file if it exists), but that would require more extensive changes with little benefit. (For example, if this function doesn't provide a WordPress version, the config doesn't have it either, meaning we can't cleanly map from a config to a docker-compose file.)
3. Avoid doing any of the shouldConfigureWp logic during wp-env start, since most of that involves internet connections (pulling docker images, downloading sources, etc.) I think it's easier to do this than to add extra checks all over the place when we do something with the network.

The side effect is that certain types of wp-env.json updates won't work if you're offline, but that seems like a reasonable compromise. For example, if you set the phpVersion, that involves downloading a different docker image. So a lot of the config options would be impacted anyways.

Testing Instructions

1. Remove core from Gutenberg's .wp-env.json file to trigger the check for the latest core source.
2. make sure that you have a wp-env environment that works
3. turn off your internet
4. run a few wp-env commands:
   • npx wp-env start
   • npx wp-env install-path
   • npx wp-env run cli bash
   • npx wp-env run cli phpunit --version

All should work.

Testing Instructions for Keyboard

Screenshots or screencast

You should see an offline message in the terminal as well: