fix: be less strict about range request responses

[costela]

The code currently only does manual byte skipping for HTTP responses with a 200 status. There are other valid status codes that may be returned for a non-range response (e.g. 203), so we should be less strict about it.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[rohitjoins]

@costela

Thank you for the PR.

Would it be possible to open a new PR from an individual-owned fork? We can't push changes to organization-owned forks like this one unless we have collaborator access. If that's not possible then we can still merge this PR but it will result in an 'evil' merge. See more info here: https://github.com/androidx/media/blob/release/CONTRIBUTING.md#push-access-to-pr-branches

Additionally, please ensure your pull request targets the main branch instead of release. All of our ongoing development and bug fixes need to be integrated into main first.

[costela]

@rohitjoins ah, my bad! Just recreated as #3410 ✔️

Closing this one in favor of the new...