Review nightly builds usage and workflow

As described in the WordPress Handbook, three different nightly builds are available:

• Point release nightlies. The current release is 6.2.2. Selecting this will put you on the track for 6.2.x development.
  (e.g., https://wordpress.org/nightly-builds/wordpress-6.2-latest.zip, API call)
• Bleeding edge nightlies. Selecting this will put you on the track for 6.3 development.
  (e.g., https://wordpress.org/nightly-builds/wordpress-latest.zip, API call)
• Beta/RC. Selecting this will update to the next released beta or RC on whichever branch you are currently running.
  (e.g., https://downloads.wordpress.org/release/wordpress-6.3-rc2.zip)

Currently, the following has been implemented and is available across Roots' packages:

• Beta/RC. 👌 Well tagged and correctly published. Nothing to do.
  • With the known limitation for the no-content edition as per https://github.com/roots/wordpress-no-content/issues/4
• Bleeding edge nightlies. 🙂 Published on main branches.
  • Their constraints (like PHP version) might be suitable to automation, but all good so far.
• Point release nightlies. ☹️ Not handled yet.
  • Could be done via 6.2-dev-ish tags (not allowed) 6.2.x-ish branches but requires automation.

Start with the WordPress Handbook section linked in the issue and compare the existing Beta/RC and bleeding-edge nightly publishing paths across Roots' packages. Investigate how point-release nightlies could follow the documented branch-development API and determine what automation is needed for 6.2.x-style branches; done means point release nightlies are published and consumable consistently.