Fix Operator agreement acceptance in Lambda runtimes

[fanny-jiang]

What does this PR do?

Add a botocore compatibility model for the AWS Marketplace Agreement operations and paginators missing from the Lambda runtime:

• CreateAgreementRequest
• AcceptAgreementRequest
• GetAgreementEntitlements
• SearchAgreements pagination
• GetAgreementEntitlements pagination

The compatibility layer patches only missing definitions and preserves definitions supplied natively by newer SDK versions. This retains botocore request validation, SigV4 signing, retries, response parsing, and paginator behavior.

The release process inlines the compatibility model into the CloudFormation ZipFile Lambda, and initialization logs report whether the compatibility model was applied. The Quick Start template version is bumped to v4.19.1.

Motivation

The Python 3.14 Lambda runtime currently bundles boto3 1.42.97. Its Marketplace Agreement model does not expose all operations and paginators required to discover, create, accept, and verify the Datadog Operator agreement. This caused EKS Quick Start onboarding to fail before the managed add-on could be installed.

Testing Guidelines

• Ran all Quick Start Python suites independently under Python 3.14: 159 tests passed.
• Verified release.sh syntax and git diff hygiene.
• Verified the injected definitions against the AWS Marketplace Agreement 2020-03-01 service and paginator models.
• Verified the rendered inline Lambda compiles and stays well below the CloudFormation inline-code size limit.
• Staging E2E with a pre-existing agreement:
  • Compatibility model applied on boto3 1.42.97.
  • The active agreement was discovered and reused.
  • Entitlement reached PROVISIONED with reason AGREEMENT_ACTIVE.
  • The root stack reached CREATE_COMPLETE.
• Staging E2E without a pre-existing agreement:
  • Active-agreement discovery returned empty.
  • The public free offer and zero-cost quote were validated.
  • A new agreement request was created and accepted.
  • Entitlement reached PROVISIONED with reason AGREEMENT_ACTIVE after approximately 86 seconds.
  • The root stack reached CREATE_COMPLETE.

Additional Notes

CloudFormation deletion continues to retain the Marketplace agreement. The compatibility layer becomes a no-op once the Lambda runtime provides all required native definitions. It can be removed, along with its tests and release inlining, after those definitions are verified across every supported Python runtime and AWS Region.

[fanny-jiang]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-27 14:14:15 UTC ℹ️ Start processing command /merge

---

2026-08-27 14:14:20 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 4m (p90).

---

2026-08-27 14:16:55 UTC 🚨 MergeQueue: This merge request is in error because of DDCI

cannot trigger DDCI.
If this continues, please let us know in #ci-infra-support with the following details:

• Head SHA of the MQ branch: e4e3b46
• Name of the MQ branch: mq-working-branch-master-96ac28c
• The DDCI Workflow from GenerateDDCIRequestFromDevflow: atlas