Use Spring's HttpRange class for range handling in APIs

A simple header converter is all that's needed, S3 API does not allow
more than one byte range.
Not sure why we had a custom range parser implementation when there's
one in the framework we depend on.

Fixes #1172 and #1131