Ensure Config Enforce Devel's form alter runs after Config Enforce's

Alright, pushed a commit to the issue fork. Going to call it a day here because brain tired but it probably needs both a test to verify that the module weight is higher than Config Enforce's and also probably invalidating the relevant cache tag for hooks/module weights because this currently requires a manual cache clear after installing to get it to actually use the new weight.

Updating title to be more accurate of what this needs to do.

This works for me locally and tests seem to be passing, but am kind of tired out after dentist so not exactly the energy to write a test for this. Maybe we can merge this and then open a follow up to add a test?

Wondering how we can actually test this because by design, the module handler service no longer provides a method to get existing implementations for a given hook in Drupal 10 → so that a fully OOP hook system has one less barrier to being implemented, so instead we could probably create a test module that implements that depends on both Config Enforce and Config Enforce Devel and \hook_module_implements_alter(), which would hopefully run after the Config Enforce Devel implementation (what do you want to bet I'll eat those words?), where we could save it to state storage; we could then invoke that hook from our test, and then check state storage for the result, asserting against the expected order.

I sat down today and figured out how to write a test for this so you're welcome merged and fixed byyyyye.

Automatically closed - issue fixed for 2 weeks with no activity.