ci: use lts/* to describe Node.js version

With this indirection, we can configure a required status check that
doesn't require updating when Node.js LTS versions change.

(The matrix version appears in the name of the
status check, this was the least-gross workaround
I could find. Peer here for some horror shows:
https://github.community/t/status-check-for-a-matrix-jobs/127354/11)

Author: ericcrosson-bitgo

.github/workflows/ci.yml

@@ -10,7 +10,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: ['12', '14', '16']
+        node-version: ['12', '14', 'lts/*']
 
     name: Node.js ${{ matrix.node-version }}
     steps:
@@ -35,7 +35,9 @@ jobs:
         uses: actions/cache@v3
         with:
           path: node_modules/.cache
-          key: turbo-${{ matrix.node-version }}-${{ github.ref_name }}-${{ github.job }}-${{ github.sha }}
+          key:
+            turbo-${{ matrix.node-version }}-${{ github.ref_name }}-${{ github.job
+            }}-${{ github.sha }}
           # According to GitHub documentation, only keys generated by the PR branch and the target branch are considered. This is
           # to prevent a malicious PR from manipulating the cache to inject malicious code into unrelated branches.
           # See: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#matching-a-cache-key