fix: byte range request end should never equal file size

[SgtPooki]

• fix: request-headers byte range parsing
• fix: response-headers byte parsing
• fix: request-headers
• fix: byteRangeContext tests
• fix: range-requests tests

Title

Fix byte range parsing

Description

Byte range requests (<range-start>-<range-end>/<size>) should never be in a state where <range-end> is greater than or equal to <size>. This PR fixes the byte range parsing in the request and response headers to ensure that the range is always valid.

Notes & open questions

More info in https://github.com/ipfs-shipyard/helia-service-worker-gateway/pull/122#issuecomment-2005215744

Change checklist

• [ ] I have performed a self-review of my own code
• [ ] I have made corresponding changes to the documentation if necessary (this includes comments as well)
• [ ] I have added tests that prove my fix is effective or that my feature works

[github-actions[bot]]

:tada: This PR is included in version 1.2.1 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

[github-actions[bot]]

:tada: This PR is included in version 1.8.0 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

[github-actions[bot]]

:tada: This PR is included in version 1.0.0 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

[github-actions[bot]]

:tada: This PR is included in version 1.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: