Fix NameError that occurs when dechunking a response that happens to
have content that looks like a term marker.
Add zero-downtime deploy to bounded pools (TORQUE-819)

Both bounded and shared pools now have a restart() method exposed via
JMX for doing zero-downtime deploys of specific subsystems (web,
messaging, jobs, etc). The next step is to add a way to trigger the
pool restart outside of JMX.
Sometimes CI takes longer than 10 seconds to spin up a jobs runtime
SharedPool#restart is a no-op if not already started (TORQUE-819)
Merge pull request #156 from tolsen/fix-dechunk-name-error

Fix NameError that sometimes occurs when dechunking a responses
Try to clean up messaging_spec on BuildHive
Move to AsyncService provided by polyglot; adjust for polyglot HASingleton API change.