Prevent premature validation in Gemini batch job operators

[daesung9511]

Move argument validation from operator initialization to execution time for GenAIGeminiCreateBatchJobOperator and GenAIGeminiCreateEmbeddingsBatchJobOperator.

Template fields are rendered after operator initialization. Performing validation in __init__ can therefore inspect unresolved Jinja expressions instead of their rendered values.

This change:

• moves the relevant validations to execute
• updates the corresponding unit tests to verify execution-time validation
• removes both operators from the operator initialization exemption list

Tests:

breeze run pytest providers/google/tests/unit/google/cloud/operators/test_gen_ai.py \
  -k "GenAIGeminiCreateBatchJobOperator or GenAIGeminiCreateEmbeddingsBatchJobOperator"

prek run --from-ref main

related: #70296

---

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

• Yes (please specify the tool below)

---

• Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines) for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
• When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number.

[shahar1]

Well done!