Set content type for AWS S3 buckets for the s3-upload goal

[Pitxyoki]

This adds the same functionality that was added by PR #27 to the AWS S3 wagon plugin, only for the S3UploadMojo class, corresponding to the s3-upload goal.

Note that the ContentTypeResolver class was moved to the cloud-storage-core module so that the code could be reused across the two plugins (Azure and S3).

[Pitxyoki]

Initially, I was doing as the PR describes. However, today I found out that the AWS S3 API can auto-determine the content-type if the upload is made by passing a reference to a File instead of an InputStream.

The current version of the PR takes advantage of that.
I'm keeping the ContentTypeResolver in the core module so that if other implementations need it, it is already available.

[gkatzioura]

Hi @Pitxyoki
I merged your other pull and is out there version 2.1.
I will check this one and get back to you

[Pitxyoki]

Hi @Pitxyoki
I merged your other pull and is out there version 2.1.
I will check this one and get back to you

Hi,
I was just checking and apparently that other PR didn't make it to 2.1. It appears it was merged to the master branch but not to 2.1 and then 2.1 was tagged and released.
Let's hope everything will be included in the next version. :-)

[DmitryKosianov]

Hi,
Are you going to merge it to the master or any release? It is pretty important update as for me. I'm using plugin version 2.3 and it still produce Content-type: application/octet-stream
just because new FileInputStream(file) is created
Hope it will be included in some nearest update

[ayozemr]

Hello! I am having problems to upload some generated docs as they are uploaded as octet-stream so index.html is downloaded instead of rendered.

Will this be released? Thanks!!