feat(jqmView): allow multiple jqm-views and jqm-panels on the same page

New features
------------

jqmView / jqmCachingView:
* jqmView and jqmCachingView are both usable
* jqmView and jqmCachingView are independent of jqmPage.
* Multiple jqmView / jqmCachingViews may be used on the same page.
* Animations can be specified on the route, on the page (`view-animation` attribute) or on the view element (via `ng-animate`)
* jqmCachingView allows animations between routes that use the same template.
  For this, add the `allow-same-view-transition` to the root element of the template.
* The route for jqmView / jqmCachingView can now be specified via data binding, i.e. independent of `$route`. This is just like `ngInclude`, but you can also specify a controller, locals and an animation
* Examples in the docs are now working with history support (back animations).
* jqmView

jqmPanelContainer:
* Multiple jqmPanelContainers may be used on the same page.
* Examples in the docs are now working
* jqmPanelContainer is independent of jqmPage.

New directive jqmScrollable
* wraps angular-scrolly.

Breaking changes
---------------

jqmViewport:
* jqmViewport directive was renamed to jqmCachingView.
* jqmView / jqmCachingView now use the term "animation" instead of "transition" (e.g. on routes, ...)
* Animation names: Use "page-slide", "page-fade", ... instead of the old "slide", ...
* Route controllers in jqmCachingView are now instantiated on every route visit and not cached. However, the underlying dom and directives are still cached.

jqmPanel:
* jqmPanel requires a jqmPanelContainer
* Changing the current panel is done with a expression for jqmPanelContainer, and not via the scope variable `$panel`, e.g.
  `<div jqm-panel-container="'left'"><div jqm-panel>...</div></div>`. This is more flexibel and simplified the code.
* Scope variable `$panel` was removed.
feat(jqmView): regression bugfixes