Installing a module in an update function should not result in automatically installing entity type/field definitions

Problem/Motivation

While working on #3084983: Move all the code related to path aliases to a new (required) "path_alias" module → we realized that installing a module in an update function should not result in automatically installing entity type/field definitions, because an update function should always install a well-defined set of entity type and definitions, to be repeatable and predictable, whereas the module installer just installs whatever definitions are available in code.

Proposed resolution

Add a flag to ModuleInstallerInterface::install() to notify that the module installation is happening in the update context, so that entity type/field definition installation can be skipped.

Remaining tasks

TODO

User interface changes

None

API changes

ModuleInstaller[Interface]::install() gets an extra optional $during_update tag. This is also passed to the various other module installation hooks.

This affects any modules extending ModuleInstaller - there are two of these - module_blacklist and disable_modules. disable_modules is abandoned in favour of config_split, module_blacklist is alpha.

There's also one module implementing ModuleInstallerInterface directly, but this is is not actually replacing the module installer so looks like a mis-use of the interface. https://www.drupal.org/project/steam_login →

Data model changes

None

Release notes snippet

TODO