Propagate verify and botocore_config in AWS Batch triggers

[KarshVashi]

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

• Adds **kwargs passthrough in both trigger __init__ methods so base-class params
  (verify, botocore_config) reach AwsBaseWaiterTrigger
• Updates both hook() methods to pass self.verify and self.botocore_config to
  BatchClientHook
• Updates operator defer sites to forward verify and botocore_config to the triggers
• Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
• Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

---

Was generative AI tooling used to co-author this PR?

• Yes - Claude Code (Opus 4.6)