FI-2961 execute preset support

[Shaumik-Ashraf]

Summary

Adds two CLI options for inferno execute:

• --preset-id that will load a preset by id from directories listed in lib/inferno/config/boot/presets.rb. This helps test kit authors.
• --preset-file that will load a preset from a given file path. This helps test kit CI users.
• Both --preset-id and --preset-file cannot be used together. However --inputs can be used with either of those options, and inputs will merge with and override presets.

Testing Guidance

1. Checkout this branch
2. Start inferno services
3. Confirm this command works:

bundle exec inferno execute --suite dev_validator --preset-id dev_validator_preset

4. Prepare another preset file, i.e: cp config/presets/dev_validator_preset.json tmp/my_preset.json. Edit the file to change its id to something else unique.
5. Confirm this command works (with the file name you used):

bundle exec inferno execute --suite dev_validator --preset-file ./tmp/my_preset.json

6. Confirm this command fails with patient not found, indicating inputs override preset:

bundle exec inferno execute -s dev_validator --preset-id dev_validator_preset -i patient_id:notfound

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.94%. Comparing base (9d0288e) to head (14cbb15).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #565      +/-   ##
==========================================
+ Coverage   83.93%   83.94%   +0.01%     
==========================================
  Files         263      263              
  Lines       11459    11460       +1     
  Branches     1261     1261              
==========================================
+ Hits         9618     9620       +2     
+ Misses       1831     1830       -1     
  Partials       10       10              

Flag	Coverage Δ
backend	92.20% <100.00%> (+0.02%)	⬆️
frontend	79.15% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[Jammjammjamm]

I think this should go the other way, so that any explicitly defined inputs override the preset.

[Jammjammjamm]

This is fine, but you shouldn't need to say self.options rather than just options unless you are reassigning it since they both refer to the same object.

[Jammjammjamm]

I find this very confusing and am having a really hard time wrapping my head around this method. Like why does this method call apply_preset, but that method isn't called anywhere if a preset id is used rather than a preset file?

[Shaumik-Ashraf]

If the CLI is invoked with --preset-file, this method will load the file into presets_repo and reassign options[:preset_id] to the id in the file. Aside from that its just bolting down some error cases.

I removed the test_session_repo#apply_preset line which I forgot to do earlier. My understanding is test_session_repo#apply_preset just adds the inputs to session_data_repo, but persist_inputs already does that in the CLI implementation (to both preset and direct inputs).