fix(ci): destroy EKS test cluster with -lock=false to survive orphaned state lock

[bhavya76]

Description of the issue

When an EKS integration test's terraform apply is killed mid-run (for example when the job's time cap SIGKILLs it while the validator is holding), it can leave an orphaned lock on the local terraform state. The teardown terraform destroy then fails to acquire the lock, so the cluster is never destroyed and leaks.

Description of changes

Add -lock=false to the EKS teardown terraform destroy, so teardown can delete the cluster even when a prior apply left an orphaned local-state lock. Teardown is the final operation on that state, so skipping the lock here is safe. terraform apply is unchanged and still locks state normally.

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tests

One-line change to the teardown step only; verified by inspection of the emitted terraform destroy command. The EKS integration job runs this destroy on teardown and exercises the change.

Requirements

Before commiting your code, please do the following steps.

1. Run make fmt and make fmt-sh
2. Run make lint

---

Integration Tests

To run integration tests against this PR, add the ready for testing label.