Create separate operation-specific configs for the Delete, Load, and Save Operations

[ashovlin]

Description

Creates new operation-specific config objects for the DynamoDB object-mapper operations.

I'm splitting this into 3 PRs:

1. Batch and Transact - Create separate operation-specific configs for the object-mapper Batch and Transact operations #3376 (this PR also contains which properties are used where)
2. Delete/Load/Save - This PR
3. Query/Scan - Create separate operation-specific configs for the object-mapper Scan and Query operations #3383

Motivation and Context

For V4 of the SDK, we're planning to split the shared DynamoDBOperationConfig object into operation-specific configs, since the shared object has grown overtime to include properties that are not relevant for all operations.

DOTNET-7513

Testing

Ran DynamoDBv2 sln tests locally

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

[philasmar]

Approved assuming you address Malhar's comments