When the Querki Server upgrades, it should force a Client upgrade

(Bug, Closed -> Fixed, Priority: High, Test Status: No automated tests yet , Reported By Justin du Coeur, )
User Interface
Summary: A problem I'm encountering frequently is that, when I've upgraded the server, my Client tabs are now stale. And since the API often changes, this causes unpredictable errors until I refresh those tabs.
Basically, we should have some kind of metadata in the communication to/from the server, about the current client and server versions. If they mismatch, force a reload of the Client.
If I'm editing, this reload should try to force a Save? Do we care enough? It's an edge case, but might occasionally be annoying.