[DX] Improve assetic dump use with composer

Possible approach for fixing dx issue with asset dumping and composer install/update.

https://jira.ez.no/browse/EZP-23492

Fixed:
- crashes when interfaces or something else needs to be cleared from prod cache on composer update
- control over when assets are dumped on composer install, as it is not needed on updates of most composer packages

Patch for ezpublish-community changing composer update to not dump assets:
```diff
diff --git a/composer.json b/composer.json
index 3c4fd1e..b01ba6c 100644
--- a/composer.json
+++ b/composer.json
@@ -91,9 +91,9 @@
             "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache",
             "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets",
             "eZ\\Bundle\\EzPublishLegacyBundle\\Composer\\ScriptHandler::installAssets",
-            "eZ\\Bundle\\EzPublishCoreBundle\\Composer\\ScriptHandler::dumpAssets",
+            "eZ\\Bundle\\EzPublishCoreBundle\\Composer\\ScriptHandler::dumpAssetsHelpText",
             "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installRequirementsFile",
            "eZ\\Bundle\\EzPublishLegacyBundle\\Composer\\ScriptHandler::installLegacyBundlesExtensions"
         ]
     },
     "config": {
```

Note: this does not mean doing composer update in production is safe, such changes should still be staged as you'll often need to also clear prod cache as well and other changes like db updates.

## Screen shoots
Shows help text on composer update first, and then the question posted on composer install:
![screen shot 2014-10-21 at 14 18 07](https://cloud.githubusercontent.com/assets/289757/4718092/06baec46-591d-11e4-949d-6f92823edf74.png)


What are the alternatives? It would be quite useful to retain possibility to have Composer run till the end without user intervention.