[O2B-1427] Store trigger configuration per runs

[martinboulais]

I have a JIRA ticket

• branch and/or PR name(s) include(s) JIRA ID
• issue has "Fix version" assigned
• issue "Status" is set to "In review"
• PR labels are selected

Notable changes for users:

• Display trigger configuration in a dedicated tab in run details page

Notable changes for developers:

• Added c++ API to update runs raw trigger configuration

Changes made to the database:

• Added column to store raw trigger configuration to runs table

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 44.02%. Comparing base (c164336) to head (8828822).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...b/public/views/Runs/Details/runDetailsComponent.js	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1848      +/-   ##
==========================================
- Coverage   44.05%   44.02%   -0.04%     
==========================================
  Files         893      893              
  Lines       15974    15976       +2     
  Branches     3014     3014              
==========================================
- Hits         7038     7034       -4     
- Misses       8936     8942       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[graduta]

Except the name convention for the data that is to be stored, PR LGTM.