feat: GitHub actions CI

[meniRoy]

run integration tests in GitHub CI actions.

I encountered an encryption error during the setup: Error while encrypting the text provided to safeStorage.encryptString. Encryption is not available.
To address this, I've added the --password-store=basic argument to the launch parameters of @vscode/test-electron, as suggested here

[meniRoy]

Create GH action CI workflow

[sagilaufer1992]

I wonder why to update the lock file, and I'm not familiar with the command you used for running the tests.
address these questions, and the rest LGTM

[sagilaufer1992]

why updating the lock file? if the package json didn't update, is there a good reason to update it for this PR?

[meniRoy]

The reason I updated the lock file is due to an error I encountered when executing pnpm install within our GitHub Actions workflow.
The error message:

Run pnpm install
 ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE  Cannot perform a frozen installation because the version of the lockfile is incompatible with this version of pnpm

Try either:
1. Aligning the version of pnpm that generated the lockfile with the version that installs from it, or
2. Migrating the lockfile so that it is compatible with the newer version of pnpm, or
3. Using "pnpm install --no-frozen-lockfile".
Note that in CI environments, this setting is enabled by default.
Error: Process completed with exit code 1.

https://github.com/env0/vscode-env0/actions/runs/5870964165/job/15919142107

[sagilaufer1992]

it seems like the installation of pnpm installed a different version than before.
you can see in our main repo, we expect to use a specific version of pnpm, specified in the package json under "engines".
make the GH action install a SPECIFIC pnpm version, that still corresponds to this lockfile, so we won't fave such issues later on in another pnpm upgrade

[meniRoy]

eb88a6f

[sagilaufer1992]

I approve, but please, if the pnpm need to be a dependency, add it, and if the lock file doesn't need to be changed, revert it

[sagilaufer1992]

can we revert the pnpm lock? or is it required now that we have pnpm as an engine?

[meniRoy]

652cbe5

[sagilaufer1992]

shouldn't it be a dev-dependency now?

[meniRoy]

pnpm is not a dev dependency its installed globally with fixed version here