Switch to HTTP/{2,3} rest bridge

[frankosterfeld]

No description provided.

[github-actions]

PR produced different images:

chart_0001.png

Got:

Expected:

Diff:

chart_fg_dipole_0001.png

Got:

Expected:

Diff:

dashboardpage_layout_0001.png

Got:

Expected:

Diff:

dashboardpage_layout_0002.png

Got:

Expected:

Diff:

dashboardpage_layout_0003.png

Got:

Expected:

Diff:

dashboardpage_layout_0004.png

Got:

Expected:

Diff:

flowgraph_0003.png

Got:

Expected:

Diff:

flowgraph_0004.png

Got:

Expected:

Diff:

keypad_0001.png

Got:

Expected:

Diff:

[frankosterfeld]

Ideally this client would also be used in the RemoteSource blocks, so we have one connection only per remote peer.

[RalphSteinhagen]

@frankosterfeld I guess this is obsolete now since your other opencmw-cpp PR#371 has been merged.

If you could confirm. Thanks in advance.

[wirew0rm]

this was only cherry-picked onto a separate branch to verify that everything works properly before merging. I've rebased and changed the reference to the current opencmw-main commit and added a flag to not run the load worker by default on deployed instances, to make this ready to be merged.

[wirew0rm]

Looks good, 3 things to follow up on in separate PRs:

• move load testing facilities into separate test binary
• make all UI requests transparent to the protocol so dashboards agnostic to the protocol instead of hardcoding RestClient
• Manage the RestClient instance:
  • share it between Blocks in the Flowgraph and the UI
  • remove the need to explicitly pass it around all the different components
  • abstraction beteween mds and http(s)2/3 clients