Improve PyDABs acceptance test consistency error (#3874)

## Changes

The PyDABs consistency acceptance test now shows actionable errors. This
PR also removes the unnecessary second test pass from `make
test-update-templates`.

**Before:** When there is an inconsistency between the yml version and
.py version of the `default` template we'd get a diff like this:
```
$ make test
[...]
>>> diff -Naur enable_pydabs=yes enable_pydabs=no
--- enable_pydabs=yes
+++ enable_pydabs=no
@@ -101,7 +101,6 @@
     "pipelines": {
       "my_pydabs_etl": {
-        "catalog": "hive_metastore",

[... 10+ more times with different line numbers like @@ -72,7... @@ -60,7... etc ...]
```

**After:** Such an inconsistency comes with a more actionable error:
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
❌ PyDABs Template Consistency Check Failed
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Python and YAML resource templates are generating different configurations!

📁 Check ALL template files in:
  libs/template/templates/default/template/{{.project_name}}/resources/
    • *.py.tmpl      (Python resource definitions)
    • *.yml.tmpl     (YAML resource definitions)

💡 Steps to fix:
   1. Look at the diff above to identify which field differs
   2. Find which *.py.tmpl file contains that field
   3. Compare it to the corresponding *.yml.tmpl file
   4. Ensure the field has the same active/commented state in both formats
```

## Why

Template inconsistencies produced cryptic diffs with no context. Second
test pass was cargo-culted from `test-update` but does nothing.

## Tests

Manual verification with intentional template inconsistency

Author: lennartkats-db

Makefile

@@ -67,8 +67,6 @@ test-update:
 # Updates acceptance test output for template tests only
 test-update-templates:
 	-go test ./acceptance -run '^TestAccept/bundle/templates' -update -timeout=${LOCAL_TIMEOUT}
-	@# at the moment second pass is required because some tests show diff against output of another test for easier review
-	-go test ./acceptance -run '^TestAccept/bundle/templates' -update -timeout=${LOCAL_TIMEOUT}
 
 # Updates acceptance test output (integration tests, requires access)
 test-update-aws:

acceptance/bundle/templates/pydabs/check-consistency/script

@@ -17,5 +17,30 @@ for enable_pydabs in yes no; do
     rm -rf my_pydabs input.json
 done
 
-trace diff -Naur enable_pydabs=yes enable_pydabs=no
+if ! trace diff -Naur enable_pydabs=yes enable_pydabs=no; then
+    cat <<'EOF'
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+❌ PyDABs Template Consistency Check Failed
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Python and YAML resource templates are generating different configurations!
+
+📁 Check ALL template files in:
+  libs/template/templates/default/template/{{.project_name}}/resources/
+    • *.py.tmpl      (Python resource definitions)
+    • *.yml.tmpl     (YAML resource definitions)
+
+🐛 Example issue: Field is ACTIVE in one format but COMMENTED in the other
+   "catalog": "${var.catalog}" vs # "catalog": "${var.catalog}"
+
+💡 Steps to fix:
+   1. Look at the diff above to identify which field differs
+   2. Find which *.py.tmpl file contains that field
+   3. Compare it to the corresponding *.yml.tmpl file
+   4. Ensure the field has the same active/commented state in both formats
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+EOF
+fi
 rm enable_pydabs=yes enable_pydabs=no