E2e tests for lambdatest

[rmccrear]

This adds e2e test on LambdaTests for the test server at https://dev.zkemail.xyz

Set the env in your bash profile before running yarn test.

# bash profile
export LT_USERNAME="username"
export LT_ACCESS_KEY="yourkey"

cd into the e2e test directory install dependencies and run the tests remotely. (The tests run separately from the rest of the project, so they get their own package.json)

cd e2e-lambdatest
yarn
yarn test

Then, you can see the results on LambdaTest's web console. Two tests will run, the UI test and the ZKP test.

Unfortunately, the ZKP doesn't seem to work on LambdaTest servers. It is terminated before finishing. This might be a limitation of the remote testing service.

[rmccrear]

Also, added a new workflow in .circleci for forge tests in src/contracts

[Divide-By-0]

Thanks! I moved the forge tests to main. Let's keep the slower lambdatest tests here until we find a way to speed it up.

one nice thing about the benchmarks is that if you create a second .add(()=>{...}) clause in a benchmark it will run a second test on the same hardware at the same time to let you compare a new implementation with an old implementation. The custom automated reporting I wrote might have to change, but it will work fine when you click the button in the browser and will print averages and variances to the console.

[Divide-By-0]

Can you try replacing the e2e lambdatest with circleci natively or browserstack or something else without the limit, and make those tests only run if all of the other tests pass first?