Tolerate malformed Content-Range in HttpIO

What does this MR do and why?

Tolerate malformed Content-Range in HttpIO

Some S3-compatible providers omit the bytes unit in Content-Range, which made Net::HTTP raise and returned a 500 when reading archived job traces. Fall back to the requested range instead.

Resolves #630433 (closed)

Changelog: fixed

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.