SignatureDoesNotMatch for presigned URL when access key contains special character (+)

[guymguym]

Environment info

• NooBaa Version: noobaa-core-5.16.0-20240310.el8.x86_64
• Platform: rhel-8

Actual behavior

1. Created an account, set the access key manually to abc+abc.
2. NOTICE - this happens when manually setting the access key, because when we generate access keys we only pick alphanumeric chars.
3. Used aws cli and cyberduck with that access key and secret without any issues (uses sigv4 in authentication header).
4. Tried to create a presigned URL with aws s3 presign s3://bucket/key but getting the URL failed with SignatureDoesNotMatch error.
5. Changed the access key to contain no +, and presign works too.
6. Tried also to get signed URL with cyberduck - the duck did not encode the + sign in the url and it messed up even before getting to the server.

Expected behavior

1. Either block using access keys with invalid chars, or make it work ok also for presigned URL.

Steps to reproduce

1. See above.

More information - Screenshots / Logs / Other output

[guymguym]

@nimrod-becker @dannyzaken didn't we fix this already?

[guymguym]

ok, so no we didn't handle this one yet. I was mixing it up with #7829.

[guymguym]

@romayalon since we will probably not fix this one, lets just make sure that for now we do not allow accepting access keys with unsupported symbols from our CLI, when keys are provided as arguments and not generated.