Shims dashboard app and uses local angular instance instead of references to global angular to be able to move this to the new platform without getting rid of angular first.

There are quite some changes outside of the dashboard app itself in here, so I'll try to put together a guide for how to review this:

• Data plugin (AppArch): filter bar directives were directly registered to uiModules which we can't use in our local angular. This PR exports the raw direcrtive definitions so they can get registered in a local angular module as well.
• Discover (KibanaApp): requireDefaultIndex magic flag on the route got removed because this requires uiRoutes we won't carry over (not used in many places anyway). The replacement is a function that has to be called in the only resolve of a route, if the returned promise resolves the actual data can be fetched. That slightly changes the code structure in discover because it was fetching the index pattern and the saved search in two separate resolve props.
• Management (AppArch): The logic redirecting to either home or the index_pattern page when there is no index pattern got moved into the requireDefaultIndex helper function.
• Visualize editor (KibanaApp): Same as for discover
• ui/capabilities/route_setup (KibanaApp/AppArch?): Got moved to src/legacy/ui/public/legacy_compat/angular_config.tsx because it's currently also using the addSetupWork hook.
• legacy_compat angular stuff (Platform?):
  • configureAppAngularModule was using NP dependencies directly, to be able to use the same function also in the new platform this was changed to take them via parameter - also be adjusted in legacy chrome src/legacy/ui/public/chrome/api/angular.js
  • Fixes a bug in the dummy wrapper route detection of local angular that resets title in some cases when moving from a dummy wrapper route to an actual angular controlled route.
  • Move ui-capability redirects here from the removed setup work
• TopNav (AppArch): Same as for the filter bar directives - exposing the directive definitions directly allows to have them registered in a local angular module just for dashboard.
• State mangement (AppArch?): Make sure the state instances only follow along but do not interfere with the URL as long as the user is within the local angular controlled prefix.
• src/legacy/ui/public/timefilter/setup_router.ts (AppArch?): Expose the logic to wire the global state instance with the NP data plugin timefilter state so it's usable in the local (and make sure it's also unsubscribing correctly)
• Graph: Pass new navigation dep through to the angular directive creation.

Dev docs

The route flag requireDefaultIndex making sure there are index patterns and the defaultIndex advanced setting is set was removed.

The same functionality can be achieved by using the helper function ensureDefaultIndexPattern from ui/legacy_compat within the resolve object of a route.