Ignore shardIterator type when sequence number is available

[KKcorps]

The PR fixes issue #7555.

The shard iterator type should be set to AFTER_SEQUENCE_NUMBER if a valid sequence number is available to start.
Otherwise, LATEST or TRIM_HORIZON should be taken based on provided shard iterator type.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 64.16%. Comparing base (493ed2c) to head (1a9b030).
⚠️ Report is 6901 commits behind head on master.

Files with missing lines	Patch %	Lines
...e/pinot/plugin/stream/kinesis/KinesisConsumer.java	0.00%	5 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (493ed2c) and HEAD (1a9b030). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (493ed2c)	HEAD (1a9b030)
unittests2	1	0

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #7592      +/-   ##
============================================
- Coverage     72.54%   64.16%   -8.39%     
- Complexity     3416     3804     +388     
============================================
  Files          1522     1543      +21     
  Lines         75905    78636    +2731     
  Branches      11093    11671     +578     
============================================
- Hits          55069    50457    -4612     
- Misses        17144    24579    +7435     
+ Partials       3692     3600      -92     

Flag	Coverage Δ
integration1	29.40% <0.00%> (-0.92%)	⬇️
integration2	27.77% <0.00%> (-1.14%)	⬇️
unittests1	68.54% <ø> (-1.31%)	⬇️
unittests2	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[npawar]

LGTm