JAMES-4231 Add S3 blob range reads

[HesandaLiyanage]

JAMES-4231 — Add S3 blob range reads

Scope

Adds the generic BlobStoreDAO.readRange contract and an S3 implementation that uses a single HTTP Range request. Range results retain the source blob metadata and expose the full object size in metadata, which lets later chunk readers interpret slot data safely.

Deliberately excluded

• ChunkMarker and BloomFilter GC handling
• BlobIdUpdater and backend metadata updates
• Compaction format/algorithm and property-based tests
• Guice wiring, WebAdmin routes, and user documentation

Design notes

• Range bounds are inclusive. end = -1 reads through the object end; a negative start requests a suffix range.
• Invalid ranges and S3 416 responses fail explicitly; no empty blob fallback is used.
• S3 uses the existing request builder, so SSE-C headers and fallback namespace handling are retained for range reads.

Tests

Added a reusable BlobStoreDAORangeReadContract and a MinIO/Testcontainers S3 implementation test covering prefix, middle, suffix, open-ended, invalid-range, metadata, and total-object-size behavior.

Tests have not been run locally.

Follow-up

JAMES-4231 — ChunkMarker and BloomFilter GC exclusion for virtual chunk addresses.