Don't run drush updb with the entity-updates flag during setup:config-import, it's dangerous

[bkosborne]

When BLT executes the setup:config-import task, it will run drush updb after importing configuration. It passes the --entity-updates flag to the updb.

I think this should be removed.

This stack overflow answer indicates that it's really a development tool and shouldn't be run under normal circumstances.

There's also a detailed change record regarding the removal of the automated entity updates system from update.php and explains why the automated update system is dangerous and shouldn't be used normally. Basically modules should handle the entity updates themselves in update hooks.

Here's an additional change record that explains the user-facing changes of the removal of the automated system.

Given that BLT's acquia cloud hooks will run the setup:config-import task during deploys, it seems dangerous to include the --entity-updates flag in the updb command.