fix s3 key handling with trailing slash

[bentsku]

Motivation

This would fix #9837. We've had multiple iterations of this, we were still unquoting the key to compare with the base_url but there was no need for it, I think this was a remnant of pre-Werkzeug 3.0

Changes

• update the logic to be more resilient in the parser (proper splitting of the path, multiple trailing slashes...)
• add more test cases

[github-actions]

S3 Image Test Results (AMD64 / ARM64)

    2 files      2 suites   3m 7s ⏱️
381 tests 331 ✔️   50 💤 0 ❌
762 runs  662 ✔️ 100 💤 0 ❌

Results for commit 1b266de.

♻️ This comment has been updated with latest results.

[coveralls]

coverage: 84.028% (+0.001%) from 84.027%
when pulling 1b266de on fix-s3-encoding
into d68c9de on master.

[github-actions]

LocalStack Community integration with Pro

       2 files  ±0         2 suites  ±0   1h 11m 18s ⏱️ -7s
2 404 tests +4  2 176 ✔️ +4  228 💤 ±0  0 ❌ ±0 
2 405 runs  +4  2 176 ✔️ +4  229 💤 ±0  0 ❌ ±0 

Results for commit 1b266de. ± Comparison against base commit d68c9de.

♻️ This comment has been updated with latest results.

[alexrashed]

Nice catch! Quite a tricky case! I only have two comments, when these are clarified we should be good to go! :) 🦸🏽