[FLINK-35022][Connector/DynamoDB] Add TypeInformed DDB Element Converter as default element converter

[vahmed-hamdy]

Purpose of the change

Add DynamoDbTypeInformedElementConverter to convert Elements to dynamoDb Sink using its provided type Info.

Verifying this change

This change added tests and can be verified as follows:

• Added unit tests

Significant changes

(Please check any boxes [x] if the answer is "yes". You can first publish the PR and check them afterwards, for convenience.)

• [ ] Dependencies have been added or upgraded
• [ ] Public API has been changed (Public API is any class annotated with @Public(Evolving))
• [ ] Serializers have been changed
• [ ] New feature has been introduced
  • If yes, how is this documented? (not applicable / docs / JavaDocs / not documented)

[dannycranmer]

Please change commit message to include the component: [FLINK-35022][Connectors/DynamoDB]

[dannycranmer]

I have left a comment regarding the need for this on the Jira: https://issues.apache.org/jira/browse/FLINK-35022

[vahmed-hamdy]

@dannycranmer Thanks for the feedback, I have addressed your comments. Alternatively I decided to follow an approach similar to RowDataToAttributeValueConverter to avoid using reflection. PTAL

[dannycranmer]

@vahmed-hamdy can you also update the docs please?

[dannycranmer]

@hlteoh37 / @z3d1k can you please take a look at this one too?

[vahmed-hamdy]

@hlteoh37 Thanks, for the feedback, the reason we took this approach is that We are trying to couple it as much as possible with Flink's TypeInfo Class, Using AttributeConverterProvider is closer to DDB's EnhancedType rather than Flink's

[vahmed-hamdy]

@hlteoh37 Do you have other comments or could we merge this PR?

[hlteoh37]

Hi @vahmed-hamdy, my preference would be for us to refactor the code in DynamoDbTypeInformedElementConverter to use a cleaner structure rather than a long list of if-else. Is this something we need to close urgently?