Enable yaml formatter; fix formatting in default-python & dbt-sql (#3026)

## Changes
- Update 'make fmt' to format yaml with
https://github.com/google/yamlfmt/
- Templates dbt-sql and default-python updated to have consistent
indentation according to formatter.

## Why
For templates with a lot of options (default-python) it's easy to
introduce formatting issues - too many empty lines or not enough in the
output. I'd like to use formatter also on non-materialized templates in
default-python/combinations to ensure that resulting yamls are formatted
well for any possible combination of options. Related:
#3004

Author: denik

.github/workflows/external-message.yml

@@ -29,25 +29,25 @@ jobs:
 
       - name: Delete old comments
         env:
-           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
-            # Delete previous comment if it exists
-            previous_comment_ids=$(gh api "repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}/comments" \
-              --jq '.[] | select(.body | startswith("<!-- INTEGRATION_TESTS_MANUAL -->")) | .id')
-            echo "Previous comment IDs: $previous_comment_ids"
-            # Iterate over each comment ID and delete the comment
-            if [ ! -z "$previous_comment_ids" ]; then
-              echo "$previous_comment_ids" | while read -r comment_id; do
-                echo "Deleting comment with ID: $comment_id"
-                gh api "repos/${{ github.repository }}/issues/comments/$comment_id" -X DELETE
-              done
-            fi
+          # Delete previous comment if it exists
+          previous_comment_ids=$(gh api "repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}/comments" \
+            --jq '.[] | select(.body | startswith("<!-- INTEGRATION_TESTS_MANUAL -->")) | .id')
+          echo "Previous comment IDs: $previous_comment_ids"
+          # Iterate over each comment ID and delete the comment
+          if [ ! -z "$previous_comment_ids" ]; then
+            echo "$previous_comment_ids" | while read -r comment_id; do
+              echo "Deleting comment with ID: $comment_id"
+              gh api "repos/${{ github.repository }}/issues/comments/$comment_id" -X DELETE
+            done
+          fi
 
       - name: Comment on PR
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           COMMIT_SHA: ${{ github.event.pull_request.head.sha }}
-        run: |
+        run: |-
           gh pr comment ${{ github.event.pull_request.number }} --body \
           "<!-- INTEGRATION_TESTS_MANUAL -->
           An authorized user can trigger integration tests manually by following the instructions below:

.github/workflows/integration-approve.yml

@@ -26,7 +26,7 @@ jobs:
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         shell: bash
-        run: |
+        run: |-
           gh api -X POST -H "Accept: application/vnd.github+json" \
             -H "X-GitHub-Api-Version: 2022-11-28" \
             /repos/${{ github.repository }}/statuses/${{ github.sha }} \

.github/workflows/integration-main.yml

@@ -30,7 +30,7 @@ jobs:
       - name: Trigger Workflow in Another Repo
         env:
           GH_TOKEN: ${{ steps.generate-token.outputs.token }}
-        run: |
+        run: |-
           gh workflow run cli-isolated-nightly.yml -R ${{ secrets.ORG_NAME }}/${{secrets.REPO_NAME}} \
           --ref main \
           -f commit_sha=${{ github.event.after }}

.github/workflows/integration-pr.yml

@@ -33,7 +33,7 @@ jobs:
       - name: Trigger Workflow in Another Repo
         env:
           GH_TOKEN: ${{ steps.generate-token.outputs.token }}
-        run: |
+        run: |-
           gh workflow run cli-isolated-pr.yml -R ${{ secrets.ORG_NAME }}/${{secrets.REPO_NAME}} \
           --ref main \
           -f pull_request_number=${{ github.event.pull_request.number }} \

.github/workflows/push.yml

@@ -14,7 +14,7 @@ on:
     branches:
       - main
   schedule:
-    - cron: '0 0,12 * * *'  # Runs at 00:00 and 12:00 UTC daily
+    - cron: '0 0,12 * * *' # Runs at 00:00 and 12:00 UTC daily
 
 env:
   GOTESTSUM_FORMAT: github-actions
@@ -192,7 +192,7 @@ jobs:
 
       - name: Verify that python/codegen is up to date
         working-directory: experimental/python
-        run: |
+        run: |-
           make codegen
 
           if ! ( git diff --exit-code ); then

.github/workflows/python_push.yml

@@ -26,7 +26,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        pyVersion: [ '3.10', '3.11', '3.12', '3.13' ]
+        pyVersion: ['3.10', '3.11', '3.12', '3.13']
 
     steps:
       - name: Checkout repository and submodules

.github/workflows/release-snapshot.yml

@@ -94,6 +94,6 @@ jobs:
           prerelease: true
           tag_name: snapshot
           token: ${{ secrets.GITHUB_TOKEN }}
-          files: |
+          files: |-
             dist/databricks_cli_*.zip
             dist/databricks_cli_*.tar.gz

.github/workflows/release.yml

@@ -161,7 +161,6 @@ jobs:
 
     needs: goreleaser
 
-
     # IMPORTANT:
     # - 'id-token: write' is mandatory for OIDC and trusted publishing to PyPi
     # - 'environment: release' is a part of OIDC assertion done by PyPi

.github/workflows/start-integration-tests.yml

@@ -37,5 +37,5 @@ jobs:
       - name: Run start_integration_tests.py
         env:
           GH_TOKEN: ${{ steps.generate-token.outputs.token }}
-        run: |
+        run: |-
           python3 ./start_integration_tests.py -R ${{ secrets.ORG_NAME }}/${{secrets.REPO_NAME}} --yes

.github/workflows/tagging.yml

@@ -11,7 +11,6 @@ on:
 concurrency:
   group: "tagging"
 
-
 jobs:
   tag:
     environment: "release-is"
@@ -47,5 +46,5 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ steps.generate-token.outputs.token }}
           GITHUB_REPOSITORY: ${{ github.repository }}
-        run: |
+        run: |-
           python internal/genkit/tagging.py