Feature/flink 18661 efo de registration

[xiaolong-sn]

What is the purpose of the change

This is the milestone of FLIP-128 to add EFO support to the FlinkKinesisConsumer.
The de-/regisiterStream operations has been introduce.
JIRA issue

Note

This PR is blocked by:

• Test coverage improvements:
  • JIRA issue
  • Pull request
• Introducing RecordPublisher.
  • JIRA issue
  • Pull request
• Add AWS SDK v2.x dependency and KinesisProxyV2
  • JIRA issue
  • Pull request
• Configuration deserialisation and validation
  • JIRA issue
  • Pull request

Brief change log

• ConsumerConstants
  • Add the describe stream and descrbie stream consumer operation parameters.
• KinesisConfigUtil
  • Add the validation of the above parameter
• FanOutStreamInfo
  • Add a new data class for storing enhanced fan-out consumer info.
• FlinkDataFetcher
  • Add a KinesisProxyV2Interface in order to register stream consumers when the efo registration mode is set to eager.
• ShardConsumer
  • Add a KinesisProxyV2Interface in order to de-/register stream consumers when the efo registration mode is set to lazy.
• KinesisProxyV2Interface & KinesisProxyV2
  • Add the de-/register stream consumer operations here.
• AwsV2Util
  • Add several methods to classify exceptions.

Verifying this change

This change added tests and can be verified as follows:

• KinesisProxyV2Test
• AwsV2UtilTest

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)