Create an official "Minor release upgrade path" initiative

The upgrade path between minor releases of D8 has hit roadblocks that has lead to many sites not upgrading, as can be seen from the D8 usage stats. There are a number of contributing factors:

• Drupal 8's migrate system includes logic for Drupal 7 contrib modules for functionality which was merged into core. OTOH there are no upgrade paths provided in core for contrib functionality merged into core during the 8+ release cycle, most notably Content Moderation, Layout Builder and Media.
• Releasing functionality in core and not supporting it with update scripts upset a lot of people. This policy has since been changed, but damage was done by it.
• A few minor releases were shipped with known backwards compatibility bugs that still haven't been fixed, e.g. https://www.drupal.org/project/drupal/issues/2906030 → and https://www.drupal.org/project/drupal/issues/2956359 🐛 2825487 broke custom formatters Needs work . While a 3rd party library can be blamed for one of the issues, it's an example of a regression between minor releases which IMHO should have been fixed immediately.

I'd like to propose the following:

1. Add an official tag for noting regressions from the previous minor release, e.g. "Minor release regression".
2. Add an official tag for noting where specific effort is required to upgrade contrib to functionality which has been pulled into core, e.g. "Contrib to core upgrade", "Contrib migrate", etc.
3. Wrap these up under an official "Minor release upgrade path" initiative. If there's an official initiative around this effort it may be possible to find additional funding to help.