Add Kinesis Data Streams trigger

[aaron-y-chen]

related: #52712

This is the first PR for Kinesis part of #52712, I will integrate the trigger with the common-messaging interface and add a system/e2e test in the next PR.

Summary

Add an asynchronous Kinesis Data Streams trigger for consuming records without occupying worker slots.

The trigger polls all shards, emits JSON-serializable record batches, handles iterator expiry, throttling, pagination, and in-run resharding, and checkpoints per-shard sequence numbers when an asset state store is available. New shards first discovered after a restart honor the configured initial position, so LATEST may skip records written during the downtime.

This is the provider-side foundation for the common-messaging integration tracked in #52712.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: [GPT 5.6-sol] following the guidelines

[aaron-y-chen]

Those failures seem to be caused by the same issue:

flit build: error: unrecognized arguments: --no-setup-py

There is already a PR to fix it: #71118

[aaron-y-chen]

Waiting for another PR #71145 to be merged.

[aaron-y-chen]

Okay, all CI failures have been fixed.

[aaron-y-chen]

Hi @jason810496, I'd appreciate it if you could take a look when you have time. :)

[vincbeck]

@seanghaeli@ramitkataria

[aaron-y-chen]

Thanks for the reviews, I believe this version is more concrete than before :)

[jason810496]

Thanks for adding the new trigger to compelete #52712.

[amoghrajesh]

Blocking due to sync access to asset state store