Move S3 operator template validation out of __init__ (#70296)

[AmoghAtreya]

Description

related: #70296 for S3DeleteObjectsOperator and ComputeEngineDeleteInstanceOperator.

Changes Made:

1. S3DeleteObjectsOperator (amazon):

   • Deferred parameter validation on template fields (keys, prefix, from_datetime, to_datetime) from __init__ into execute().
   • Updated unit tests in tests/providers/amazon/aws/operators/test_s3.py to assert parameter checks occur during execution rather than constructor time.

2. ComputeEngineDeleteInstanceOperator (google):

   • Deferred GcpBodyFieldValidator instantiation out of __init__ and into execute() so api_version is evaluated after Jinja rendering.
   • Added unit tests in tests/providers/google/cloud/operators/test_compute.py verifying validator instantiation occurs inside execute().

3. CI Exemptions:

   • Removed both path::ClassName entries from scripts/ci/prek/validate_operators_init_exemptions.txt.

works on: #70296

---

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

• Yes (Claude Sonnet)

Generated-by: Claude following the guidelines

---

[AmoghAtreya]

Sorry, the issue has been linked to the PR and should be unlinked to prevent the issue from closing. My apologies.

[shahar1]

Sorry, the issue has been linked to the PR and should be unlinked to prevent the issue from closing. My apologies.

No worries, it's a matter of changing the "resolves:" into "related:" :)
Also, I've modfied the title - we don't use conventional commits.
Please note that you have a failure in the static checks.

[AmoghAtreya]

Thanks for updating the title. Will commit the code to fix the failure in the static checks after they all finish running. The Tests (AMD) check was failing due to an incorrect number in the code.

[AmoghAtreya]

@shahar1 please let me know if there's anything you want me to change in this PR. I fixed all the static bugs and checks from a few days ago.

[shahar1]

Could you please focus the PR on a single provider? (I know that GCP compute operators are being handled in another PR, so maybe just focus on S3DeleteObjectsOperator)

[AmoghAtreya]

Reverted changes! This PR is only focused on S3 now. @shahar1

[AmoghAtreya]

Checks just passed. Please let me know what you think!

[shahar1]

#70505 narrows the rule: field is None checks read provision, not the un-rendered value, so they belong in init. This one qualifies.

Please keep both copies, though. keys = self.keys or self.hook.list_keys(prefix=..., ...) lists the whole bucket when every filter is None — reachable past a correct constructor check, since a templated keys can render to None under render_template_as_native_obj=True. The execute() guard catches that; the __init__ guard keeps the plain authoring mistake a parse-time error.

The exemption entry can still go — the hook just doesn't see comparisons inside a comprehension:

by_scan = prefix is not None or from_datetime is not None or to_datetime is not None
if not exactly_one(keys is not None, by_scan):
    raise ValueError("Either keys or at least one of prefix, from_datetime, to_datetime should be set.")

Identical on every input including keys=[]. Context in #70296's "False positives" section.

Drafted-by: Claude Code (Opus 5); reviewed by @shahar1 before posting

[AmoghAtreya]

Just committed the change for that. Updated 'S3DeleteObjectsOperator.init' to use explicit 'is not None' checks while retaining execution-time guards as requested by you @shahar1. This change has been committed and is dependent on #70505 being merged.