fix: keep product.json file permissions in release

When we added the change to modify the `package.json` version using `mv`
and `jq` we didn't account for lost file permissions.

This caused a bug only happening in CI.

This should fix it by giving it 755 via `chmod`.

.github/workflows/build.yaml

@@ -296,7 +296,7 @@ jobs:
     name: Run e2e tests
     needs: build
     runs-on: ubuntu-latest
-    timeout-minutes: 15
+    timeout-minutes: 25
     steps:
       - name: Checkout repo
         uses: actions/checkout@v3

.github/workflows/release.yaml

@@ -322,6 +322,8 @@ jobs:
           echo "Updating version in lib/vscode/product.json"
           tmp=$(mktemp) 
           jq '.codeServerVersion = "$VERSION"' release/lib/vscode/product.json > "$tmp" && mv "$tmp" release/lib/vscode/product.json
+          # Ensure it has the same permissions as before
+          chmod 755 release/lib/vscode/product.json
 
       - name: Compress release package
         run: tar -czf package.tar.gz release

ci/build/build-vscode.sh

@@ -42,6 +42,12 @@ main() {
 
   pushd lib/vscode
 
+  if [[ ! ${VERSION-} ]]; then
+    echo "VERSION not set. Please set before running this script:"
+    echo "VERSION='0.0.0' yarn build:vscode"
+    exit 1
+  fi
+
   # Set the commit Code will embed into the product.json.  We need to do this
   # since Code tries to get the commit from the `.git` directory which will fail
   # as it is a submodule.
@@ -90,6 +96,8 @@ main() {
 EOF
   ) > product.json
 
+  chmod +x product.json
+
   # Any platform here works since we will do our own packaging.  We have to do
   # this because we have an NPM package that could be installed on any platform.
   # The correct platform dependencies and scripts will be installed as part of