Fix S3 filenames that include a hash

[cyreb7]

Ran into this when we switched to using Zip Stream recently, S3 filenames with a hash # were being truncated. The Laravel Storage facade handles hashes without issue.

Possible breaking changes I can think of with this PR:

1. Using strlen("s3://{$this->getBucket()}/"); means that if anyone has a malformed S3 bucket string, this would fail in unexpected ways
2. If anyone was relying on the old behavior of parse_url(), this does change how S3 file paths are parsed

[jszobody]

See #110

[cyreb7]

Oh gosh, sorry, I didn't see that PR. I don't mind if you want to close this, but I'd argue that while AWS doesn't recommend hashes, they do support it. Plus at least two people have run into this in the wild and had the motivation to open a PR to fix it, so it's clearly a real-world issue.

Did you ever look into using the AWS parser? If you did, then we could at least bug AWS support instead of you 😆