Always use path style endpoints

Problem/Motivation

Bucket names with a "." will not work with s3fs_cors. The reason is that "https://www.example.com.s3.dualstack.amazonaws.com/" does not have a valid SSL certificate because of the dots in the name. Only "https://www-example-com.s3.dualstack.amazonaws.com/" will work, as the SSL certificate only matches the "https://*.s3.dualstack.amazonaws.com/" name.

People won't know about this problem until they start using s3fs_cors. It also will cost them time to figure out the problem as it is not obvious.

You can enable the use_path_style_endpoint of s3fs, but that has its own problems with s3fs, and I prefer to have it disabled.

IMO there is no good reason for s3fs_cors not to use path style endpoints all the time, so that is what this tiny patch does. It will use "https://s3.dualstack.amazonaws.com/www.example.com/"

Steps to reproduce

Use a bucket with a dot in it.

Proposed resolution

Always use path style endpoints.