Disable Terraform state locking in CI to resolve lock conflicts

Remove state locking from terraform plan commands in GitHub Actions workflow to prevent lock conflicts between local development and CI runs. This is a temporary measure to ensure CI can run reliably for testing scenarios.

- Changed -lock-timeout=5m to -lock=false in both terraform plan commands
- This allows CI to run without waiting for state locks to be released

Author: jameslaneovermind

.github/workflows/automatic.yml

@@ -78,7 +78,7 @@ jobs:
         id: plan
         run: |
           set -o pipefail -ex
-          terraform plan -compact-warnings -no-color -input=false -lock-timeout=5m -out tfplan 2>&1 \
+          terraform plan -compact-warnings -no-color -input=false -lock=false -out tfplan 2>&1 \
             | tee terraform_log
           terraform show -json tfplan > tfplan.json
 
@@ -154,7 +154,7 @@ jobs:
         id: plan-cost
         run: |
           set -o pipefail -ex
-          terraform plan -compact-warnings -no-color -input=false -lock-timeout=5m -out tfplan-cost 2>&1
+          terraform plan -compact-warnings -no-color -input=false -lock=false -out tfplan-cost 2>&1
           terraform show -json tfplan-cost > tfplan-cost.json
 
       - uses: overmindtech/cost-signals-action@v1