Module Cleanup

Lists uninstalled or deleted modules with leftover transient data and allows the admin to delete any leftover data. A fix for Module 'module_name' has an entry in the system.schema key/value storage.
A fix for The 'module_name' entity type does not exist error. The module with the entity must be installed.

Added a fix for No available releases found in version 1.0.3. As a side note, there is most likely a module you have installed that is causing this error. You may want to record what configurations and entities you have saved and turn the modules off and on till you find out what module is causing the errors.

Added a fix for How to fix "non-existent config entity name returned by FieldStorageConfigInterface::getBundles()" in version 1.0.6. The fix uses a logger service that listens for a log to watchdog, so when you run cache clear or install a module it automatically cleans up the error. The module will display a message at the top of the install page when you install this module if there was an error that was fixed.

Drush Commands
Command: modcup:delete-config: Deletes left over data after a module is uninstalled. One required parameter. Parameter is the module machine name.
Alias: modcup-dc

Command: modcup:field-purge-batch: Runs field_purge_batch(1000) only and outputs errors as messages.
Alias: modcup-fpb

Command: modcup:create-storage: Creates a field storage only. Two required parameters. 1st parameter is the field name. 2nd parameter is the entity type.
Alias: modcup-cs

Command: modcup:delete-field: Runs field_purge_batch(1000), creates a field storage if needed and then deletes the field and field storage. The module with the entity must be installed. Two required parameters. 1st parameter is the field name. 2nd parameter is the entity type.
Alias: modcup-df

Command: modcup:clear-updates: Cleans up No available releases found errors in Available updates.
Alias: modcup-cu

Install with composer
Enable module
Go to Configuration->System->Delete transient module data