refactor(JADS): Refactor to use JADS web server as a grunt plugin

Convert JADS script to a Grunt Task - published on npmjs.org as grunt-jads.
Refactor the Gruntfile.js for generated apps to use the new grunt task.
feat(server): Enable grunt-jads to serve generated apps

grunt-jads is a grunt plugin wrapper for JADS (Just Another Development Server: https://github.com/bocallaghan/JADS). It uses the node express module to setup a web server. Run with 'grunt server'.
To enable url aliases on the server changes were required to the generated Gruntfile to set the alias paths based on the UI5 location entered by the user.
script-base.js was also changed to enable this.
Added .jsbeautifyrc files to the project so that we can decide where and when the jsFormat'ing applies. This was necessary otherwise the generated Gruntfile would look ugly with the format on save option. So now - for general development: format_on_save is true. However in the templates directory, format_on_save is false. You can still format by right-clicking and choosing format and even narrowing it down by selecting specific text.
Fixed issues https://github.com/saschakiefer/generator-openui5/issues/28 by removing references to sapui5 and replacing with openui5.
Adding grunt-jads closes issue: https://github.com/saschakiefer/generator-openui5/issues/25.
refactor(gruntfile): change grunt-jads usage to lower-case
fix(fiori app): Fix generated title for fiori apps

Fiori apps were being generated with a fixed title. Changed to dynamic based on application name prompt in the generator. Fixed issue: https://github.com/saschakiefer/generator-openui5/issues/27.
fix(tests): fixed generator tests failing since UI5 library options were added

The app-classic and app-fiori-master-detail tests needs the prompts added for the UI5 library options. Added to current pull-request: https://github.com/saschakiefer/generator-openui5/pull/31
chore(build): Remove support for Node.js 0.8.0 as per Yeoman toolset

After recent update to Yeoman, some node dependencies now only work on Node.js 0.10 and above.
feat(build): Switch from grunt-jads to grunt-contrib-connect.

Switched from our basic grunt-jads Node.js http server to grunt-contrib-connect. grunt-contrib-connect coupled with grunt-connect-proxy and grunt-contrib-watch combine to enable live reloading of code changes with a Node.js web server that can handle https and proxying resources.
Changed the UI5 location code to simply enter the bower location or the direct location entered by the user (typically the remote sap server). No url aliases are setup. If necessary the user can still easily set them up by specifying further base locations in the grunt-contrib-connect task.
Completes:
https://github.com/saschakiefer/generator-openui5/issues/29
https://github.com/saschakiefer/generator-openui5/issues/30
feat(build): enable livereload of xml views
feat(gen): html page to demo web proxy capabilities.

This page is not setup for scaffolding by the generator yet. It needs to be refactored as per @qmacro's single page app architecture. I've put it in here so as not to lose it for now...
refactor(gen): refactor the generated gruntfile without the web proxy as default.

Our current generated apps don't require a proxy out-of-the-box so set the gruntfile this way - no need instantiating one for no reason. However, in future, generated apps that do require proxy services will enable this via generator promtps.
merge build_process changes into develop

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.