fix: Add IPV4 Range Filtering for Backblaze B2 API Integration

[AnthonyRoss]

Currently the B2 Native API only supports IPV4 and Facebook requires IPV6. This change forces an IPV4 DNS resolution when looking up the B2 Authorize endpoint DNS.

This change was tested locally by running the BackblazeIntegrationTest while setting java.net.preferIPv6Addresses=true

BUILD SUCCESSFUL in 1s
24 actionable tasks: 2 executed, 22 up-to-date
INFO 2025-07-25T12:07:22.601918-05:00 Region extracted from s3ApiUrl: us-east-005
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
DEBUG 2025-07-25T12:07:22.961639-05:00 Uploading 'test-upload-1753463242960' with file size 14 bytes

[lisad]

@AnthonyRoss I think the lint failure just requires changing the commit message to meet the Conventional Commit format - https://www.conventionalcommits.org/en/v1.0.0/

[AnthonyRoss]

fix: Add IPV4 Range Filtering for Backblaze B2 API Integration

I think this new commit message should fix it: e257f02