make router.ts + normalize how we handle routes + queries etc

[spencercap]

i've never seen vue-router used how it's currently setup... let's make it more standard.

• introduce <router-view /> compeonent
• add named router views for panels operating independently, like:
  • https://router.vuejs.org/guide/essentials/named-views.html#nested-named-views
  • https://codesandbox.io/s/nested-named-views-vue-router-4-examples-re9yl?initialpath=/settings/emails&file=/src/views/UserSettings.vue

@enceladus what's the reasoning for search being part of the route instead of a query string? name: 'full', path: '/:ledger/contract/:contractId/s/:query', component: App i think router.resolve() is a helpful util we should leverage instead of the getNewRoute method in state.ts

[spencercap]

• [ ] hide show panels
• [x] focus search w keyboard shortcuts

[spencercap]

• [ ] make ability to minimize modular panels
• [ ] highlight particular panel w hash # + mod-fund
• [ ] share state thru url WITH modular panel settings in URL (share button generates url + copies to clipboard)

[spencercap]

consider when modal=about2 returns a not real modal. close the modal in this case... + remove modal qs