Database update step for `drush deploy` behaves differently than `drush updb --no-cache-clear` about drush

[spleshka]

This may be the reason why some devs recommend running drush cr before drush deploy to make sure that cache of services definitions is flushed before running database updates (which would fail otherwise for cases like the one described above). The fix provided in the PR hopefully removes the need of cache rebuild before the deploy command, but we were not entirely sure about potential side effects of adding #[CLI\Kernel(name: 'update')] to the deploy command, especially in the environments where cache is moved to the memory storages.

During testing of the change we've spotted that drush updb --no-cache-clear command flushes cache bins anyway, so presumably it's safe to keep #[CLI\Kernel(name: 'update')] for all use cases, but an additional confirmation would be greatly appreciated.

[weitzman]

#5953 fixed this