feat(lambda): add SQS provisionedPollerConfig support with validation and fix type mismatch

[badmintoncryer]

Issue # (if applicable)

Follow-up to #37197 (see lpizzinidev's review comment).

Reason for this change

In #37197, lpizzinidev pointed out two issues:

1. minimumPollers and maximumPollers in stream.ts were declared as required, while the definition in event-source-mapping.ts has them as optional — a type mismatch.
2. The JSDoc for these properties did not document the differences in allowed ranges and default values between Amazon SQS and Amazon MSK / self-managed Kafka / Amazon MQ.

Additionally, SqsEventSource did not support provisionedPollerConfig at all, and SQS has stricter limits than MSK/Kafka (minimum value of 2 vs 1).

Description of changes

• aws-lambda-event-sources/lib/stream.ts: Changed minimumPollers and maximumPollers from required to optional to match event-source-mapping.ts. Added Valid Range to JSDoc and a @see link.
• aws-lambda/lib/event-source-mapping.ts: Updated JSDoc for both properties to document service-specific valid ranges and defaults (SQS: min 2–200 default 2, max 2–2000 default 200 / MSK/Kafka/MQ: min 1–200 default 1, max 1–2000 default 200).
• aws-lambda-event-sources/lib/sqs.ts: Added provisionedPollerConfig to SqsEventSourceProps with SQS-specific validation (min: 2–200, max: 2–2000) and wired it through to EventSourceMapping.

Describe any new or updated permissions being added

None.

Description of how you validated changes

Added unit tests for all new validation paths.

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

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
This security report is NOT a review blocker. Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ☑️	Skipped	Failed ❌️
Security Guardian Results	48 ran	47 passed		1 failed

Test	Result
Security Guardian Results
packages/@aws-cdk-testing/framework-integ/test/aws-lambda-event-sources/test/integ.sqs-with-poller-config.js.snapshot/lambda-event-source-sqs-with-poller-config.template.json
sqs-encryption-enabled.guard	❌ failure

• View Security Guardian Results

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
This security report is NOT a review blocker. Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ☑️	Skipped	Failed ❌️
Security Guardian Results with resolved templates	48 ran	47 passed		1 failed

Test	Result
Security Guardian Results with resolved templates
packages/@aws-cdk-testing/framework-integ/test/aws-lambda-event-sources/test/integ.sqs-with-poller-config.js.snapshot/lambda-event-source-sqs-with-poller-config.template.json
sqs-encryption-enabled.guard	❌ failure

• View Security Guardian Results with resolved templates