chore(deps): update dependency boto3 to v1.36.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
boto3	==1.35.96 -> ==1.36.0

---

Release Notes

boto/boto3 (boto3)

v1.36.0

Compare Source

======

• api-change:apigateway: [botocore] Documentation updates for Amazon API Gateway
• api-change:bedrock-agent-runtime: [botocore] Now supports streaming for inline agents.
• api-change:cognito-identity: [botocore] corrects the dual-stack endpoint configuration
• api-change:partnercentral-selling: [botocore] Add Tagging support for ResourceSnapshotJob resources
• api-change:s3: [botocore] This change enhances integrity protections for new SDK requests to S3. S3 SDKs now support the CRC64NVME checksum algorithm, full object checksums for multipart S3 objects, and new default integrity protections for S3 requests.
• api-change:security-ir: [botocore] Increase minimum length of Threat Actor IP 'userAgent' to 1.
• api-change:sesv2: [botocore] This release introduces a new recommendation in Virtual Deliverability Manager Advisor, which detects elevated complaint rates for customer sending identities.
• api-change:workspaces: [botocore] Added GeneralPurpose.4xlarge & GeneralPurpose.8xlarge ComputeTypes.
• api-change:workspaces-thin-client: [botocore] Mark type in MaintenanceWindow as required.
• enhancement:AWSCRT: [botocore] Update awscrt version to 0.23.4
• feature:s3: [botocore] The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using the when_supported and when_required options - in code using the response_checksum_validation parameter for botocore.config.Config, in the shared AWS config file using response_checksum_validation, or as an env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.
• feature:s3: [botocore] Added support for the CRC64NVME checksum algorithm in the S3 client through the optional AWS CRT (awscrt) dependency.
• feature:s3: [botocore] S3 client behavior is updated to always calculate a CRC32 checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). Checksum behavior can be configured using when_supported and when_required options - in code using the request_checksum_calculation parameter for botocore.config.Config, in the shared AWS config file using request_checksum_calculation, or as an env variable using AWS_REQUEST_CHECKSUM_CALCULATION. Note: Botocore will no longer automatically compute and populate the Content-MD5 header.

v1.35.99

Compare Source

=======

• api-change:gamelift: [botocore] Amazon GameLift releases a new game session placement feature: PriorityConfigurationOverride. You can now override how a game session queue prioritizes placement locations for a single StartGameSessionPlacement request.
• api-change:route53: [botocore] Amazon Route 53 now supports the Mexico (Central) Region (mx-central-1) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region

v1.35.98

Compare Source

=======

• api-change:artifact: [botocore] Support resolving regional API calls to partition's leader region endpoint.
• api-change:bedrock: [botocore] With this release, Bedrock Evaluation will now support latency-optimized inference for foundation models.
• api-change:ec2: [botocore] Add support for DisconnectOnSessionTimeout flag in CreateClientVpnEndpoint and ModifyClientVpnEndpoint requests and DescribeClientVpnEndpoints responses
• api-change:kafkaconnect: [botocore] Support updating connector configuration via UpdateConnector API. Release Operations API to monitor the status of the connector operation.
• api-change:transcribe: [botocore] This update provides tagging support for Transcribe's Call Analytics Jobs and Call Analytics Categories.

v1.35.97

Compare Source

=======

• api-change:redshift: [botocore] Additions to the PubliclyAccessible and Encrypted parameters clarifying what the defaults are.
• api-change:securitylake: [botocore] Doc only update for ServiceName that fixes several customer-reported issues
• api-change:sts: [botocore] Fixed typos in the descriptions.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.