When stomp not reachable, blueapi churned through 20,000 DataCollectionIDs in 5 minutes

[DiamondJoseph]

On i22 over the weekend (TODO: attach logs from k8s) stomp was temporarily unavailable. In that time, blueapi was either falling over when trying to send documents or otherwise failing after requesting a new data collection ID from the numtracker service. Plans should fall over when they try to use infrastructure that is not available.
The failing plan was the inner part of a for loop, unsure why it didn't fail the whole plan.

Steps To Reproduce

def my_plan() -> MsgGenerator:
    yield from count([some_detector])

Run a plan similar to the above with STOMP disconnected.

Acceptance Criteria

• Stomp disconnect should result in a plan falling over