feat(lambda): lambda esm features

[Abogical]

Reason for this change

Error handling

The following new properties to Kafka based ESM for error handling is now supported:

• BisectBatchOnFunctionError
• MaximumRetryAttempts
• MaximumRecordAgeInSeconds
• FunctionResponseTypes

Poll grouping

Add support for multi esm grouping which can allow customers optimize for cost by sharing compute.
This will only be supported for Kafka based ESMs in provisioned mode. This support is added via the new property ProvisionedPollerConfig

Failure destination

Allow customers to send failed records to a kafka topic using on failure destination. We'll be supporting same cluster as the event source.

Description of changes

• Adds the new properties mentioned above.
• For setting failure destination:
  • Created a new kafka-dlq file to support new destination
  • Customers can either define topicName or kafka://topic as input.
  • Added unit tests and integration tests.

Describe any new or updated permissions being added

No new permissions are added.

Description of how you validated changes

Verified through integration and unit tests.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #36164 has been dequeued. The pull request rule doesn't match anymore. The following conditions don't match anymore:

• -label~=(blocked|do-not-merge|no-squash|two-approvers)
• check-success=build
• check-success=validate-pr
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue priority-squash]
    • -label~=(blocked|do-not-merge|no-squash)
    • check-success=build
    • check-success=validate-pr
    • any of: [🛡 GitHub branch protection]
      • check-neutral = validate-pr
      • check-skipped = validate-pr
      • check-success = validate-pr
    • any of: [🛡 GitHub branch protection]
      • check-neutral = build
      • check-skipped = build
      • check-success = build.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.