AWS S3 Binding - Add Content-Type in the metadata request

[luigirende]

Description

With this PR is possible add the Content-Type header when creates the object in the storage

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[ItalyPaleAle]

Please fix the DCO failure: https://docs.dapr.io/contributing/contributing-overview/#developer-certificate-of-origin-signing-your-work

[luigirende]

Hi @ItalyPaleAle, i've just updated the code from your suggestions and signed-off the commit. Let me know if it's okey

[berndverst]

@luigirende the "sign-off" is not applied to all commits.

To add your Signed-off-by line to every commit in this branch:

Ensure you have a local copy of your branch by checking out the pull request locally via command line.
In your local branch, run: git rebase HEAD~3 --signoff
Force push your changes to overwrite the branch: git push --force-with-lease origin main

[ItalyPaleAle]

@luigirende the linter is reporting some issues

[luigirende]

@ItalyPaleAle there are 2 issues on test task, I don't know how to fix them.

[ItalyPaleAle]

@ItalyPaleAle there are 2 issues on test task, I don't know how to fix them.

Thanks for fixing the linter errors! Those are unrelated - some tests are flaky

[berndverst]

Thanks again for this.

In the future please open an issue for discussion before making a PR and allow for maintainers or other Dapr users to leave comments. Or make a PR for an issue which has already been open for some time (and then link to that issue in your PR).