CI to Build and Unit Test Various Components on Pull Requests

[spoonincode]

Add a CI workflow that builds and runs unit tests on each pull request. TrustEVM is somewhat of a "monorepo" -- it contains multiple projects that are built independently of each other. To start with, we should build and run unit tests for the following three components (anyone feel free to chime in with more that are good in the initial scope). What we don't want in this initial CI scope is a full integration test that deploys all the components, stands up a chain, etc. That might be a good thing to have (eventually) but this ticket is not it.

1. The TrustEVM node
   This ought to be buildable with effectively a cmake && make in the root directory. Exact dependencies required are unknown to me (I believe it's expected to compile on ubuntu 20 at least? There is no README yet making stuff like this clear). Also unknown to me if there are any unit tests.
2. Contract & Contract Unit Tests
   The contract is in contract/ and needs to be built with cdt, and the unit tests are in contract/tests which use the Native Contract Unit Tester. These are two separate cmake projects and be aware the tests assume where the contract build directory was placed in. Most likely this should leverage the same pattern as eos-system-contracts to fetch cdt & leap-dev.deb.
3. Gateway Proxy & Tests
   This is in peripherals/gateway_proxy. The gateway proxy "driver" is Javascript requiring node16(+?) & nginx, but the tests are in C++ and require C++20 & boost 1.75+. Even Ubuntu 22.10 is still stuck on boost 1.74 so Ubuntu will not be usable here unless you build boost.

It's possible this all ends up as one workflow with a bunch of jobs. Or separate workflows for each component. Or even one root workflow activated on a PR that then calls other separate "reusable" workflows for each project. Left to the implementer to decide best approach.

Due to the repo being private, and the reportedly long build and/or test times, we may want to consider using ENF runners until the repo is public. However, the ENF runner fleet has stringent maximum run times (lowtier being the longest at 60 minutes) so we may need adjustments to the fleet.

See Also

• TrustEVM
  • Pull Request 277 - Create a .gitignore
  • Pull Request 278 - Delete Circle CI Config
  • Pull Request 291 - TrustEVM Node CI
  • Pull Request 293 - TrustEVM Contract CI
  • Pull Request 301 - Expand .gitignore
  • Pull Request 311 - Remove -Deosio_DIR cmake Flag from Contract Tests
  • Pull Request 312 - Run TrustEVM Contract Tests in CI
  • Issue 332 - Add tests/leap/nodeos_trust_evm_test.py to CI
  • Issue 333 - Resolve CMake Dependency Issues
• github-app-token-action

  Each of these PRs were PRed upstream as well.

  • Pull Request 1 - Security - Bump json5 from 1.0.1 to 1.0.2
  • Pull Request 3 - Documentation
  • Pull Request 4 - Security - Address CVE-2022-46175 in json5
  • Pull Request 5 - Security - Upgrade octokit/auth-app from 4.0.7 to 4.0.9 to Address CVEs

[spoonincode]

The Gateway Proxy has been removed from the project, and #283 has already removed it from the repo. No need for that piece in CI now.

[heifner]

Please add running of: tests/leap/nodeos_trust_evm_test.py. The directions for running it can be found in the comment at the top of the python file.