Disabled FORCE_COLOR on setup-node GitHub Action

refs #13716
refs actions/setup-node#317 (comment)

- the `setup-node` GitHub Action seems to use a shell command to get the
  cache path, but these are colorised when `FORCE_COLOR` is enabled
- this causes the Action to fail to read the path correctly
- the comment referenced above suggests to remove `FORCE_COLOR` but it's
  nice to have colored output for our tests
- instead, I'm disabling the environment variable on the `setup-node`
  action so it still works
- I've tested with the referenced PR and this unblocks dependency caching 🎉

.github/workflows/canary.yml

@@ -12,6 +12,8 @@ jobs:
           fetch-depth: 0
           submodules: true
       - uses: actions/setup-node@v2
+        env:
+          FORCE_COLOR: 0
         with:
           node-version: '14.17.0'
 

.github/workflows/release.yml

@@ -17,6 +17,8 @@ jobs:
           fetch-depth: 0
           submodules: true
       - uses: actions/setup-node@v2
+        env:
+          FORCE_COLOR: 0
         with:
           node-version: '14'
 

.github/workflows/test.yml

@@ -18,6 +18,8 @@ jobs:
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v2
+        env:
+          FORCE_COLOR: 0
         with:
           node-version: '14.17.0'
       - run: yarn
@@ -49,6 +51,8 @@ jobs:
           fetch-depth: 0
           submodules: true
       - uses: actions/setup-node@v2
+        env:
+          FORCE_COLOR: 0
         with:
           node-version: '14.17.0'
 
@@ -90,6 +94,8 @@ jobs:
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v2
+        env:
+          FORCE_COLOR: 0
         with:
           node-version: ${{ matrix.node }}
 
@@ -174,6 +180,8 @@ jobs:
           fetch-depth: 0
           submodules: true
       - uses: actions/setup-node@v2
+        env:
+          FORCE_COLOR: 0
         with:
           node-version: '12.22.1'
       - run: npm install -g ghost-cli@latest