add metadata to saved params json file

[yiwen-h]

Closes #299

Note that with this PR, we will be adding metadata to two different files. For example for a scenario with name example in v3.2, for provider XYZ, with runtime runtime, metadata will be added to both of these files in the results storage container:

• old format of results file, saved in prod/v3.2/XYZ/example-runtime.json.gz - we will deprecate this in the medium to long term
• new params.json file, saved in aggregated-model-results/v3.2/XYZ/example/runtime/params.json

Does this work @matt-dray ?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (022aa8b) to head (16541b7).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #306   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           18        18           
  Lines          999      1002    +3     
=========================================
+ Hits           999      1002    +3     

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

🚀 New features to boost your workflow:

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

[tomjemmett]

I thought we was going to add the metadata as columns to the parquet files? The metadata will be "lost" as soon as a file is downloaded as it's only a function of azure storage.

[matt-dray]

Both, basically. Exposing the metadata on params.json is still needed to help us produce things like the outputs reports, the mitigator comparison app and the tagged runs report.

[yiwen-h]

Yes we did that already here @tomjemmett #296

[tomjemmett]

Ah cool, must have forgot or missed that! Checked for issues, but if it's already done... 😝