Fix signature mismatch bug due to max size bytes header

[thclark]

Summary

In the previous release 0.18.0, the addition of the X-Goog-Content-Length-Range header was "fixed". Previously it had been incorrectly added and was thus always missing.

However, this header must be identically both:

• Encoded into signature generation and
• Set on the upload request

The "fix" in 0.18.0 added it into the encoding of the signature generation but did not set it on the upload request. The resulting code caused errors in all uploads using the widget.

This release fixes that problem by clarifying the default value and ensuring that the correct header is set on upload. In the event that the requested max_size_bytes is 0, the upload size is unlimited.

This release adds a setting GCP_STORAGE_BLOBFIELD_MAX_SIZE_BYTES allowing you to set a maximum for all your blobfields. However, to avoid a breaking change, the default is set to 0 (unlimited).

Contents (#86)

Fixes

• Correctly implement of max_size_bytes to avoid signature mismatch

Operations

• Update ruff to sort imports in precommit
• Update to latest stack

Style

• Format all files per pre-commit specs