To debug the 4.2 sharded failures in the driver:

• The spec organizer needs to be extracted into shared tooling
• Subsequently, it needs to be augmented to support running the segments of the test suite (or report what those segments are)