The "moderation_state" base field overrides cause install from existing config to fail

Updated patch with just a new config archive (the previous one was not sorted correctly). Please review

Those config archive are hard :)

Hm, I think test with fixtures should go to the module

The last submitted patch, 48: 3129874-48.patch, failed testing. View results →

Per #39

Should we find a way to throw an exception when a base field override is created, to prevent these leaking into installations in other ways? If we're doing this, it'd be nice to confidently say: there is never a BFO for any CM field, on any installation.

Do we need an update hook to delete the existing ones?

We're missing test coverage that asserts the option is missing from the UI and no BFO entities are created when submitting the UI.

Don't think these have been answered yet.

I updated the patch for the Drupal 10.3.x compatibility. Thank you!

Last patch doesn't fix the issue.
Currently this issue only gets fixed if we manually remove `*.moderation_state.yml` from config folder. We might need new patch to fix this issue.
I've checked in 10.2.x version.

#54, see #37, the current patch only prevents moderation_state BFOs to be exported. Existing ones need to be removed manually.
Let's not continue with patches and create a merge request.