make tabs.js just another screen_view

[dominictarr]

I think we should treat tabs as just another screen view. and use the # in the browser as a way to set UI state, that way, we can link to {bootstrap_server}#{invite_code}#{welcome_message} and you'll be able to send someone that code, get them in the network, and then lead them to an welcome message from you explaining what you have just gotten them into.

It also means the UI is highly composable, which is surely a good thing. This does also means we'll need to refactor some stuff that assumes tabs is the top level and a singleton.

[dominictarr]

i.e. how state is persisted, and how keyboard events are persisted.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.