[META-0] CMI path to beta

As of today, @alexpott recommended the following order for next steps:

1. Dependency management stuff:
   • #2080823: Create API to discover config entities' soft dependencies and use this to present a confirm form on module uninstall
   • #2030073: Config cannot be imported in order for dependencies?
2. #2004370: Batch the configuration synchronisation process
3. #1808248: Add a separate module install/uninstall step to the config import process

@alexpott, @mtift, @GaborHojtsy, and myself reviewed all of our current beta blockers yesterday. Updated plan in the summary.

The name in parentheses for each issue is the issue owner.

Also, several issues currently tagged "beta blocker" are not listed and are being de-scoped from the beta. @alexpott is following up on these issues individually.

Where does #2198429: Make deleted fields work with config synch go?

#2161591: Change default active config from file storage to DB storage is likely to end up being a beta blocker, but doesn't block any other CMI work AFAIK, though it would have to be made to work with #2224887: Language configuration overrides should have their own storage I think. Adding it to the list so that it stays on our radar.

Ah, that's much easier to read. :)

The name in parentheses is the beta blocker owner in our beta release management, not necessarily the same as the assignee.

Removing the beta blocker tag, since this itself is not actually blocking the beta and we know where to find it. ;) Unlike some other metas where the problem space is not well-defined, issues only make it onto this list once they're already tagged as beta blockers themselves.

Leaving at critical for visibility, because it is.

/train

I've left this open for our beta target issues.

Time to call this fixed.

See you in #2345225: [meta-0] CMI path to release!