Re-assess patches in composer.json and remove where possible

Problem/Motivation

Super short version: cweagans/composer-patches that we require is breaking DrupalCI and there's no way to add it to the allow list before DrupalCI does the composer install. For details, see #3307885: Customize DrupalCI config to allow running cweagans/composer-patches; fails otherwise

Steps to reproduce

Run DrupalCI, get Composer require error.

Proposed resolution

Re-assess which patches we need and whether a new version of a dependency can be required that includes those patches, eventually removing cweagans/composer-patches so that we can run DrupalCI.

Multiselect module

We currently require version 8.x-1.2 of this which is the latest of that branch; this doesn't contain the fixes we use patches for; the 2.x branch which (at time of writing) has a beta release does contain the fixes from the patches.

• #2852660: CSS need improvement, causes field following multiselect to wrap which is a duplicate of #2981851: Floats not cleared which is in the beta.
• #3130242: No schema for multiselect.settings is in the beta.

It doesn't look look like either issue is necessary for Config Enforce Devel to function, so we could expand the version constraint to add ^2.0 and remove the patches, and most or all users will get the newer version with the fixes while technically not breaking backwards compatibility with Drupal 8, which has been end of life for months now.

Configuration development module

This one is likely to be the blocker as it doesn't look like the maintainers are present much or at all going back two or three years. Neither of these are even merged, though there is recent activity:

• #3296836: Automated Drupal 10 compatibility fixes - This is mostly done but some problems with Drupal core version constraints at time of writing. We could go without it, but then we would't be able to support Drupal 10.0 anymore until it's merged. Update: has been merged.
• #3163349: Define hooks to provide 'auto_import' and 'auto_export' - This is one is necessary for Config Enforce Devel to function. We should contribute to cleaning up the code in this issue and add some tests for the hooks.

We'll probably have to reach out the maintainers of the module to get these issues looked at once they're ready. We could also ask to be added as maintainers if they don't have time, maybe just temporarily to get these done and released, and then they can remove us as maintainers unless one or more of us have the bandwidth to help out in their issue queue.

Remaining tasks

Do the things.

User interface changes

Minimal or none, depending on Multiselect.

API changes

None?

Data model changes

None?