Migrate polybft e2e framework to edge

[vcastellm]

Description

Backport the e2e framework + tests from v3 to edge.

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)

Breaking changes

Please complete this section if any breaking changes have been made, otherwise delete it

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

Manual tests

Running in local

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (feature/v3-parity@d5ff74c). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head b7b8af3 differs from pull request most recent head 92dcc55. Consider uploading reports for the commit 92dcc55 to get more accurate results

@@                 Coverage Diff                  @@
##             feature/v3-parity     #797   +/-   ##
====================================================
  Coverage                     ?   46.48%           
====================================================
  Files                        ?      157           
  Lines                        ?    20803           
  Branches                     ?        0           
====================================================
  Hits                         ?     9670           
  Misses                       ?    10430           
  Partials                     ?      703           

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

[Stefan-Ethernal]

Generally looks good, but not sure if we should strive to consolidate existing edge framework with this one somewhere in the future?

And just not to forget: we need to port bridge test (and bridge e2e testing framework infrastructure).

[vcastellm]

Generally looks good, but not sure if we should strive to consolidate existing edge framework with this one somewhere in the future?

Yeah, this should be our goal, but it will be out of the scope in this PR, we still have some work to do, but anyway, the existing e2e framework in edge is going to be removed at some point.

And just not to forget: we need to port bridge test (and bridge e2e testing framework infrastructure).

Same here, pending to do.

[Stefan-Ethernal]

LGTM, although it would be nice to address the some of the issues reported by gosec:

• [/github/workspace/e2e-polybft/framework/test-cluster.go:129] - G301 (CWE-276): Expect directory permissions to be 0750 or less (Confidence: HIGH, Severity: MEDIUM)
• [/github/workspace/e2e-polybft/framework/test-cluster.go:100] - G304 (CWE-22): Potential file inclusion via variable (Confidence: HIGH, Severity: MEDIUM)
• [/github/workspace/e2e-polybft/framework/test-cluster.go:100] - G302 (CWE-276): Expect file permissions to be 0600 or less (Confidence: HIGH, Severity: MEDIUM)...

[goran-ethernal]

LGTM. As Stefan said, it would be nice to fix those gosec errors. Not sure about these snyk tests, we can not see their execution 😕

[vcastellm]

Snyk tests are about some outdated dependencies we have in general across the repo, we'll need to address them in following PRs

[Kourin1996]

Looks good to me.