Website should use persistent remctl connections
Currently each remctl from the website requires a new connection and handshake to the remctl server. These are slow, typically taking on the order of 0.5-1 seconds to do the initial handshake.
We should take advantage of some bindings to the C API to use persistent connections instead of shelling out to the remctl command. Notably, the new 2.13 release of remctl includes Python bindings. We should possibly backport those and use them.