Separate DynamoDBOperationConfig Into Operation-Specific Configs

[ashovlin]

Description

Merging the feature branch into v4-development. This combines #3380, #3387 , #3383, and #3376

Motivation and Context

#1748 - DynamoDBOperationConfig is shared amongst the object-persistence methods, but has become overloaded over time, with some properties only applying to some operations.

This moves us towards new, operation-specific config objects. We've marked methods that take DynamoDBOperationConfig as deprecated in V4, but are not planning to remove them entirely yet. We may do so in a future major version.

See the description of #3376 for a longer explanation of which properties are relevant to which operations.

Testing

PENDING DRY-RUN

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed

License

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

[96malhar]

@ashovlin Can you rebase your PR and address the merge conflicts? I imagine the sooner this is done the better it is since new stuff is constantly being merged in v4-development

[ashovlin]

Rebased on current v4-development, and dry run 9fa7b1ed-5a5d-4a0e-86b5-5e5521b2525e passed.