In SERVER-84353, it was discovered that it was fairly difficult (with today's infrastructure) to reliably setup a testing scenario where read tickets are exhausted.

Write a utility function, with stated requirements and leveraging the novel mechanism invented in SERVER-84353, that allows an author to exhaust read tickets before executing a testing scenario.

Additionally - write a few tests (or a suite?) that uses this to provide more testing coverage. I don't believe there is currently any explicit coverage of exhausted read tickets.

Question: should exhausted write tickets be tested? Is that covered today?