Automating e2e tests

[vcastellm]

Description

This is the first of a series of PRs to bring e2e testing to Edge, in this PR we enable automation of running e2e tests with GH actions.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

Documentation update

Updated e2e/README.md

Additional comments

One e2e test is failing, now detected because automation, but fixing the test itself is out of the scope of this PR.

[vcastellm]

Additional comment: It looks like there's a flaky test in e2e

[codecov]

Codecov Report

Merging #769 (c242c09) into develop (49b9e68) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #769   +/-   ##
========================================
  Coverage    52.71%   52.72%           
========================================
  Files          130      130           
  Lines        17147    17147           
========================================
+ Hits          9039     9040    +1     
  Misses        7460     7460           
+ Partials       648      647    -1     

Impacted Files	Coverage Δ
network/server.go	75.75% <ø> (-0.43%)	⬇️
network/server_discovery.go	75.79% <0.00%> (+1.91%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Stefan-Ethernal]

Generally looks good, but posting comments with observations.

[ferranbt]

LGTM!

[Kourin1996]

Thank you for PR! I've left only suggestions. Please check and change if you feel need. Thank you

[Stefan-Ethernal]

Also just another general feedback on e2e framework refactoring, which we can decide later on...

On v3, we have introduced abstractions for cluster and bridge and I'd say that looks better than implementing all those functions, which don't belong to the TestServer itself in the helper.go (test-cluster.go, test-bridge.go etc.)

[zivkovicmilos]

Looks good 💯

[vcastellm]

@Stefan-Ethernal on that observation, the corresponding abstraction to test-cluster here would be https://github.com/0xPolygon/polygon-edge/blob/develop/e2e/framework/ibft.go#L19 and I can move the resolve function up there and pass it as config to the test server, as I did in the #771, I'd say, let's go with this now, and I would propose this refactor in that PR to see how it looks.

[ZeljkoBenovic]

Great job. 🥇
Left a minor comment.