Upgrade to Pants 2.17.0 (#35)

This updates this repo to Pants 2.17, via 2.16.

Upgrading to 2.16 requires adjusting for the new approach to tools (no "tool lockfiles").

.github/workflows/pants.yaml

@@ -26,7 +26,7 @@ jobs:
     - uses: actions/setup-python@v4
       with:
         python-version: ${{ matrix.python-version }}
-    - uses: pantsbuild/actions/init-pants@v4-scie-pants
+    - uses: pantsbuild/actions/init-pants@v5-scie-pants
       # This action bootstraps pants and manages 2-3 GHA caches.
       # See: github.com/pantsbuild/actions/tree/main/init-pants/
       with:
@@ -35,7 +35,7 @@ jobs:
         gha-cache-key: v0
         # The Python backend uses named_caches for Pip/PEX state,
         # so it is appropriate to invalidate on lockfile changes.
-        named-caches-hash: ${{ hashFiles('lockfiles/*.txt') }}
+        named-caches-hash: ${{ hashFiles('lockfiles/*') }}
         # If you're not using a fine-grained remote caching service (see https://www.pantsbuild.org/docs/remote-caching),
         # then you may also want to preserve the local Pants cache (lmdb_store). However this must invalidate for
         # changes to any file that can affect the build, so may not be practical in larger repos.
@@ -50,9 +50,10 @@ jobs:
       run: |
         pants --version
     - name: Check BUILD files
-      run: pants tailor --check update-build-files --check
+      run: |
+        pants tailor --check update-build-files --check ::
     - name: Lint and typecheck
-      run: | 
+      run: |
         pants lint check ::
     - name: Test
       run: |