Job Upgrade Status: Variable MODULE_NAME should be overridable and the drush command should also work for themes

Migrated issue

Reported by: jurgenhaas

Related to !237 (merged)

Problem/Motivation

This job uses the environment variable MODULE_NAME as an argument for a number of drush commands. The value of that variable comes from the hidden job fragment .create-environment-variables where it derives it from the CI project name.

The problem is, that the module name doesn't always have to be the same as the project name. Therefore, it should be possible that a project's configuration can explicitly provide the module name as a variable.

Also, the upgrade status job enables the module, but that needs to behave differently, if the project contains a theme and not a module.

Proposed resolution

Allow a project to define the _MODULE_NAME variable and use that as the MODULE_NAME instead of the project name. And then also determine if the project is a module or a them and then use the correct drush command to enable one or the other.