Added HTTP bridge pipeline to system tests in GitHub actions

[ppatierno]

This PR tries to add the bridge pipeline to the GitHub actions as we were used to have within Azure pipelines.

[scholzj]

You realize the Bridge pipeline was used exactly twice ... once in 2023 and once in 2024? :-o

[ppatierno]

You realize the Bridge pipeline was used exactly twice ... once in 2023 and once in 2024? :-o

I can't see it as a reason for not having it defined, if it doesn't hurt. Otherwise please gives me a technical reason. Thanks.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.01%. Comparing base (6d21795) to head (d02ebc8).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #12591      +/-   ##
============================================
+ Coverage     74.99%   75.01%   +0.01%     
- Complexity     6432     6435       +3     
============================================
  Files           373      373              
  Lines         24904    24904              
  Branches       3205     3205              
============================================
+ Hits          18677    18681       +4     
+ Misses         4907     4905       -2     
+ Partials       1320     1318       -2     

see 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[scholzj]

I can't see it as a reason for not having it defined, if it doesn't hurt. Otherwise please gives me a technical reason. Thanks.

I just wanted to confirm you know how much it was used. There is no need to reply this way!

[im-konge]

As I mentioned to you in our offline discussion, you can do this by specifying profile when triggering the pipeline. However if you want to have it consistent, I don't see an issue not having it there.

The changes LGTM. Thanks

[Frawless]

I am fine with that, but we should probably improve the process of running custom pipelines. The discussion is still in progress on strimzi-dev slack.