Support the ability to run e2e tests on different testbeds/NICs

[akiselev1]

This PR will address #139

The proposed solution uses a new label (e2e-test-710) to initiate a e2e flow on 710-labelled runner. The original e2e-test label is used to run test on a 810-labeled runner. Manual trigger (workflow_dispatch) allows to choose wither 810 (default) or 710 NIC hw to run. All scenarios were tested in my fork: akiselev1#1

[dkosteck]

Overall looks good, just my one comment which is optional/something to consider

[akiselev1]

@jianzzha - please take a look

[jianzzha]

I'm not sure I like the idea of duplicating the same code in different workflow files. If more NIC are added, then more duplication ... Instead, I think we should explore an idea of dynamic setting of runs-on

[akiselev1]

I'm not sure I like the idea of duplicating the same code in different workflow files. If more NIC are added, then more duplication ... Instead, I think we should explore an idea of dynamic setting of runs-on

I don't like it either. I spent a day experimenting with workarounds. As I mentioned in the PR description:

Unfortunately it is not possible to parameterize "runs-on" value for github action flow due to this known issue: actions/runner#480 . Existing workarounds work only for a single label or require 2 files per flow.

[jianzzha]

Looks ok. The last line of duplicate code is a trade off for less complexity and we can live with that

[dkosteck]

Looks good to me, we may want to explore the default label if/when we end up with more cards/testbeds, but for now this makes sense