fix(thread-dump-lambda): Align awscli/boto3 and group them in Dependabot

awscli 1.x and boto3 share botocore/s3transfer, so Dependabot bumping
either one alone caused pip ResolutionImpossible (awscli 1.45.25 needs
s3transfer>=0.18 while boto3 1.43.14 needs <0.18). awscli is required
(eks_client.py imports awscli.customizations.eks.get_token), so it
cannot be removed.

Bump both to the compatible .25 release (verified resolves: botocore
1.43.25, s3transfer 0.18.0) and add a Dependabot group so awscli and
boto3 always update together, preventing recurrence. Supersedes #838
and #839.

Author: Yuriy Bezsonov

.github/dependabot.yml

@@ -24,6 +24,15 @@ updates:
     directory: "/infra/scripts/setup/thread-dump-lambda"
     schedule:
       interval: "monthly"
+    groups:
+      # awscli and boto3 share botocore/s3transfer; they must bump together
+      # or pip resolution fails. Group them into a single PR.
+      aws-python:
+        patterns:
+          - "awscli"
+          - "boto3"
+          - "botocore"
+          - "s3transfer"
   - package-ecosystem: github-actions
     directory: "/"
     schedule:

infra/scripts/setup/thread-dump-lambda/requirements.txt

@@ -1,4 +1,4 @@
-boto3==1.43.14
+boto3==1.43.25
 kubernetes==36.0.0
-awscli==1.45.14
+awscli==1.45.25
 requests==2.34.2