Support ability to rename fields and deprecate existing names; does so for S3

[jeffalder]

Description

When renaming properties via customization.config, the existing names can be deprecated.
On S3 CopyObjectRequest, deprecates bucket in favor of destinationBucket and key in favor of destinationKey.

Motivation and Context

This covers half of the requests in #1313 .

Testing

Added tests for deprecation
Validated resulting CopyObjectResult class

Screenshots (if appropriate)

n/a

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed
• A short description of the change has been added to the CHANGELOG
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[jeffalder]

@millems Here ya go! Have at it. Thanks for your lightning-fast turnaround on feedback, too!

[millems]

Looking great, right off the bat. Just one small comment. Thanks for all your contributions!!

[jeffalder]

I added the bean-style setters. Then I realized that there was a gap in the logic for lists and maps; I updated the checks to make sure that lists and maps can't be deprecated (yet), along with enum types.

[millems]

Nice testing! Thanks for your contribution.