Fixes #5685

The addition of presigned s3 urls caused some complications that broke the s3 upload. Somehow minio handles url encoding slightly differently which is why we didn't catch it.

Changes made to fix it:

• '?' is no longer allowed in s3 urls by default: the first occurence of a ? will be considered the start of the query param string, like a regular url.
• to present those who really want to use '?'s in their s3 urls, theres now a s3_url_compatibility_mode option that can be set to disable query params and globs on s3 urls.

While simply disallowing '?' in s3 urls may seem a bit crude, we already did not really support them well as they would be seen as glob characters and would be able to cause unexpected behaviour.

To in short:

By default, Globbing and Query params for fully qualified urls are enabled

SELECT * FROM "s3://bucket/path/file*.parquet?s3_region=eu-west-1";

optionally, you can use the compatibility mode to reach those hard to reach places

SET s3_url_compatibility_mode=true;
SELECT * FROM "s3://bucket/path/an?awfully*named[file].parquet";

If you were using ? in globs on s3 urls, the workaround is to use the [abcde] notation to catch single characters.