chore: fix Windows builds + upgrade esy (#87)

.ci/utils/use-esy.yml

@@ -1,5 +1,5 @@
 # steps to install esy globally
 
 steps:
-  - script: "npm install -g @esy-nightly/esy"
+  - script: "npm install -g esy@beta"
     displayName: "install esy"

.ci/utils/use-node.yml

@@ -2,6 +2,6 @@
 
 steps:
   - task: NodeTool@0
-    displayName: "Use Node 8.x"
+    displayName: "Use Node 20.x"
     inputs:
-      versionSpec: 8.x
+      versionSpec: 20.x

.github/workflows/build.yml

@@ -7,15 +7,15 @@ jobs:
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
-        os: [ubuntu-20.04, macos-11]
+        os: [ubuntu-latest, macos-latest, windows-latest]
     steps:
       - uses: actions/setup-node@v2
         with:
           node-version: '18'
       - uses: actions/[email protected] 
 
       - name: Install esy
-        run: npm install -g @esy-nightly/esy
+        run: npm install -g esy@beta
 
       - name: Try to restore install cache
         uses: actions/[email protected]

azure-pipelines.yml

@@ -14,12 +14,12 @@ jobs:
   - template: .ci/build-platform.yml
     parameters:
       platform: Linux
-      vmImage: ubuntu-18.04
+      vmImage: ubuntu-latest
 
   - template: .ci/build-platform.yml
     parameters:
       platform: MacOS
-      vmImage: macOS-11
+      vmImage: macOS-latest
 
   # Need windows-2019 to do esy import/export-dependencies
   # which assumes you have bsdtar (tar.exe) in your system
@@ -28,7 +28,7 @@ jobs:
   - template: .ci/build-platform.yml
     parameters:
       platform: Windows_x64
-      vmImage: windows-2019
+      vmImage: windows-latest
 
   # This job is kept here as we want to have the platform names in the same file
   - job: Release
@@ -38,7 +38,7 @@ jobs:
       - MacOS
       - Windows_x64
     pool:
-      vmImage: macOS-11
+      vmImage: macOS-latest
       demands: node.js
     steps:
       - template: .ci/cross-release.yml