Previously replaced a large swatch of the initial websockets implementation with polling in #91

Currently websockets has become more cumbersome than it is beneficial:

• Requires a separate implementation to "sync" authentication with regular session when client connects (more code to maintain)
• Client is not actually using benefits of bi-directional communication -- its only used for server -> client updates
• Requires more configuration/setup for reverse-proxy which is a barrier to easy deployment
• Recently, for some reason, even though it is only being used on the status page for receiving opStats updates it is sending a massive amount of data.

It would be a better develop experience to just remove it entirely and replace it with another polling implementation.