Fix Nuxt SSR hydration issue

[shanejearley]

Nuxt provides useState composable to create a reactive and SSR-friendly shared state across components. In other words, it's an SSR-friendly ref replacement. But there seems to be an issue with our implementation of it... and we end up with two copies of our Nuxt page slot displaying in the browser at once, one from the server and one from the client.

We need to isolate this issue by doing a few things first:

• Remove the current workaround code, which is the client-only tag wrapped around the slot tag in ./layouts/default.vue
• Remove template bindings and add them back incrementally to see which piece of code breaks the app's state and creates both the server and client to render

**Note: ** It should be related to trying to modify our composable state in the template in a way that makes Nuxt break.