Reduce the amount of HTTP polling required #8
Description
Currently, every process that wants to make use of this needs to query the Http endpoint individually. Rate Limiting indicates that we can only make 5 requests per second to this endpoint per VM.
As we trust everything else that's running on the VM, we want to use some form of Named Pipe infrastructure to facilitate the communication. The first process to run wants to take some form of global cross-process lock, and then that process will be responsible for querying the Http endpoint and broadcasting the resulting body across a named pipe. If a process starts up and it is unable to acquire the global lock then it wants to be a listener on the named pipe. These processes should also periodically check to see if the global lock can be acquired, in case the first process has finished and released the lock.