Consolidate auto.offset.reset config

[jeffxiang]

This PR removes the offset.reset.strategy TieredStorageConsumer config and consolidates it with native KafkaConsumer's auto.offset.reset config. The old model of having both configs makes it confusing and difficult to understand the consumer's offset reset behavior, especially with different TieredStorageModes.

Now, the TieredStorageConsumer will only accept the native KafkaConsumer's auto.offset.reset config, and use it throughout the consumer logic. The previous TieredStorageConfig offset.reset.strategy (if supplied) will be ignored.

The way we use this config is as follows:

mode = KAFKA_ONLY

• The auto.offset.reset config will be passed directly into the native KafkaConsumer, resulting in the same behavior as regular KafkaConsumer

mode = KAFKA_PREFERRED

• The auto.offset.reset config provided by the user-supplied Properties will be first extracted and stored as a field
• We will internally override this config to be none when passing it into the KafkaConsumer, to ensure that KafkaConsumer.poll() will throw OffsetOutOfRangeException if the offset is out of range, instead of automatically resetting offsets within the KafkaConsumer
• If KafkaConsumer.poll() throws an OffsetOutOfRangeException, we fall back to S3Consumer.poll() as we did previously
• If any S3PartitionConsumer.poll() encounters a NoSuchKeyException (the S3 version of OffsetOutOfRange), we will reset offsets based on the auto.offset.reset config supplied by the user, or throw the exception as an OffsetOutOfRangeException if the user supplied auto.offset.reset=none

mode = TIERED_STORAGE_ONLY

• This mode is untested / under development

[vahidhashemian]

Minor nit inside.

Since this is a breaking change, I'd suggest documenting how to switch from old version to the new and if different circumstances could affect how that switch should be done.

[vahidhashemian]

nit: If strings like "latest" or "none" are used in multiple places, I'd suggest using a global constant for them.