Disabling the default target module causes issues

Problem/Motivation

Coming from 🐛 Enforced config registry in active config does not get removed when target module is uninstalled Closed: works as designed , it appears that we are allowed to disable the default target module, which then causes some problems.

Steps to reproduce

1. Enable Config Enforce Devel
2. Observe that a default target module is created
3. Uninstall the default target module
4. ???

Proposed resolution

To resolve this bug directly, we can probably hook into the uninstall process and check if the default target module is being uninstalled, and stop it from being uninstalled.

We should also considering no longer generating a default target module altogether, and instead print warnings that link to the form to create your first target module, etc. This will avoid the need to uninstall (and eventually delete) a target module that is no longer required.

Remaining tasks

TBD

User interface changes

TBD

API changes

N/A?

Data model changes

N/A?