The QuiescenceController is already written, but not yet integrated with the handle lifecycle of transactions, rounds, or the block stream. Whether through direct (i.e. in BlockStreamManagerImpl itself) or indirect (e.g. a listener) means, this task is for hooking up all the disparate pieces of the quiescence implementation such that the network can quiesce or break quiescence as needed.

There may be additional touchpoints with the handle workflow itself. If desired these can be split out into other sub-tickets, or handled as part of this one.