Move Compute Engine validation out of constructors

[daesung9511]

Move Compute Engine input validation and template-dependent transformations out of operator constructors.

The affected operators previously performed validation and derived values such as resource_id during init. Because template fields are rendered after operator initialization, this caused validation and transformation logic to run against unrendered values.

@shahar1

This change:

• Move Compute Engine input validation from operator constructors to execution time
• Defer template-dependent transformations, including resolving resource_id from rendered body fields
• Create body validators after template rendering
• Preserve runtime validation for existing Compute Engine start and stop operators
• Update unit tests to verify validation during execution
• Remove the corresponding operators from the constructor logic exemption list

Tests:

breeze testing providers-tests providers/google/tests/unit/google/cloud/operators/test_compute.py

related: #70296

---

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

• Yes (please specify the tool below)

---

[shahar1]

Well done! Minor comments to handle and we're good to go

[shahar1]

Great!!!