Add yamlfmt precommit hook (#2584)

Co-authored-by: Shuchang Zheng <wintonzheng0325@gmail.com>

.github/workflows/sdk-release.yml

@@ -1,5 +1,4 @@
 name: Build Skyvern SDK and publish to PyPI
-
 on:
   workflow_dispatch:
   push:
@@ -7,7 +6,6 @@ on:
       - main
     paths:
       - 'pyproject.toml'
-
 jobs:
   check-version-change:
     runs-on: ubuntu-latest
@@ -17,7 +15,6 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 2
-
       - name: Check if version changed
         id: check
         run: |
@@ -35,12 +32,10 @@ jobs:
             echo "Version remained at $CURRENT_VERSION"
             echo "version_changed=false" >> $GITHUB_OUTPUT
           fi
-
   run-ci:
     needs: check-version-change
     if: needs.check-version-change.outputs.version_changed == 'true'
     uses: ./.github/workflows/ci.yml
-
   build-sdk:
     runs-on: ubuntu-latest
     needs: [check-version-change, run-ci]
@@ -48,13 +43,11 @@ jobs:
     steps:
       - name: Check out Git repository
         uses: actions/checkout@v4
-
       # If you wanted to use multiple Python versions, you'd have specify a matrix in the job and
       # reference the matrixe python version here.
       - uses: actions/setup-python@v4
         with:
           python-version: "3.11"
-
       # Cache the installation of Poetry itself, e.g. the next step. This prevents the workflow
       # from installing Poetry every time, which can be slow. Note the use of the Poetry version
       # number in the cache key, and the "-0" suffix: this allows you to invalidate the cache
@@ -65,7 +58,6 @@ jobs:
         with:
           path: ~/.local
           key: poetry-1.7.1
-
       # Install Poetry. You could do this manually, or there are several actions that do this.
       # `snok/install-poetry` seems to be minimal yet complete, and really just calls out to
       # Poetry's default install script, which feels correct. I pin the Poetry version here
@@ -80,7 +72,6 @@ jobs:
           version: 1.7.1
           virtualenvs-create: true
           virtualenvs-in-project: true
-
       # Cache your dependencies (i.e. all the stuff in your `pyproject.toml`). Note the cache
       # key: if you're using multiple Python versions, or multiple OSes, you'd need to include
       # them in the cache key. I'm not, so it can be simple and just depend on the poetry.lock.
@@ -90,27 +81,22 @@ jobs:
         with:
           path: .venv
           key: pydeps-${{ hashFiles('**/poetry.lock') }}
-
       # Install dependencies. `--no-root` means "install all dependencies but not the project
       # itself", which is what you want to avoid caching _your_ code. The `if` statement
       # ensures this only runs on a cache miss.
       - run: poetry install --no-interaction --no-root
         if: steps.cache-deps.outputs.cache-hit != 'true'
-
       # Now install _your_ project. This isn't necessary for many types of projects -- particularly
       # things like Django apps don't need this. But it's a good idea since it fully-exercises the
       # pyproject.toml and makes that if you add things like console-scripts at some point that
       # they'll be installed and working.
       - run: poetry install --no-interaction
-
       - name: Clean dist directory
         run: rm -rf dist
-    
       - name: Build Package
         run: poetry build
-
       - name: Publish to PyPI
         env:
           TWINE_USERNAME: __token__
           TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
-        run: poetry run twine upload --repository pypi dist/*
+        run: poetry run twine upload --repository pypi dist/*