cim should not run on site:build

[peteratdennis]

When using drupal site:build the command drush cim -y is run which effectively does, in drupal 7 language, features revert all.
This means that if a configuration is change on live it will be lost on the devs vm and consequently on the next release.
So drush cim -y should not run on the VM, it still must run on live however.

[davidgrayston]

Perhaps make this optional, e.g. --skip-cim or --skip-config-import, as I'd imagine in most cases we would want this to behave the same as pre-production and production environments.

Alternatively, we could opt in to cim, e.g. --import-config on VM, however, this would mean we have to manually import config every time we build a site on the VM.

cc @marcelovani

[marcelovani]

done, see pr #55
usage: drupal site:build --skip="config:import"