Attach a life-cycle to default assets and then move the state to PUBLISHED (Allows default assets to be visible in the Store)

Changes
-The store deployer.js files have been disabled (The script is present,but the deploying logic has been disabled)
-The assets (ebooks,gadgets and sites) folders have been copied to publisher/config/defaults/
-Added a check to ensure that the life-cycle is not loaded more than once into memory during the /modules/publisher TenantCreate event


Additions:
-Two new scripts have been added to the modules folder (bundler.js and asset.depolyment.js).These are used to load and deploy assets
-Added a defaultAssets block to the config/publisher-tenant.json.This is used to control the deployment of default assets. (Allows certain asset types and individual assets to be ignored during deployment)
-Added a hierachical install scripting mechanic which allows users to modify the way a default asset is deployed by selectively overriding a method (Please refer to the config/defaults/ folder for the structuring of the install.js scripts)
-The default asssets are only deployed for the Super Tenant in response to the TenantLoad event