Use sha384 signatures for list requests

[tim-kos]

Summary

• switch listRequest() signature generation from SHA-1 to SHA-384
• include the sha384: algorithm prefix for list-request signatures
• add regression tests for:
  • sign() uses sha384 with prefix
  • listRequest() uses sha384 with prefix

Why

api2 issue https://github.com/transloadit/api2/issues/5337 tracks SDK support for SHA-384 signatures.

The Go SDK already used SHA-384 for normal request signing, but listRequest() still used SHA-1 without a prefix. This made signature behavior inconsistent and could break accounts defaulting to SHA-384.

Notes

• Smart CDN signing remains unchanged (SHA-256).

[kvz]

@tim-kos note that we at least need 256 for CDN support

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.60%. Comparing base (62a7440) to head (be28507).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   82.60%   82.60%           
=======================================
  Files           6        6           
  Lines         345      345           
=======================================
  Hits          285      285           
  Misses         32       32           
  Partials       28       28           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.