Make config enforcement during cache-rebuild optional

I hate to be a wet blanket, but this broke our tests because the testbot (rightfully) can't find the use Drush\Drush; added in config_enforce.module, because it's not listed in our composer.json dependencies - nor should it be listed since we only provide an optional Drush command that the module works perfectly fine without.

Is there a reason we even need to explicitly call Drush::logger()? Outside of the Drush command, this module shouldn't need to know about or care about the existence of Drush; at least, that's how I look at it. If the problem that it's solving is to show output from running the enforcement, might it not be better to see if it's possible to somehow get the log messages from our logger channel that were generated between before we do the enforce and after it's done, or something like that? After a bit of digging, it looks like Drush even provides a service that sounds like it might be for what we're trying to do.

I missed the dependency on Drush in ✨ Import configs when modules are enabled Active . Fixed in latest commit and marked as "Needs review" to re-test.

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