Updating tests for stability

[bistline]

This fixes two tests that have become unstable in recent weeks.

1. StudyValidationTest#test_should_fail_all_ingest_pipeline_parse_jobs: a race condition is happened during cleanup after failed parse jobs. The files are correctly marked as 'failed', but underlying source data doesn't always clean up in time before an assertion is checked. A 5 second sleep has been added to help avoid this
2. SummaryStatsUtilsTest#test_should_get_data_retention_policy_report: depending on what other test suites have been run before this test, the number of expected studies can change. Now, a query is run to get the correct number and all mocks are assembled to avoid errors.

Lastly, the --disable-frozen-string-literal cli option has been set for the Terra Orchestration smoke test to avoid polluting the log with /usr/local/rvm/rubies/ruby-3.4.2/lib/ruby/3.4.0/open-uri.rb:455: warning: literal string will be frozen in the future (run with --debug-frozen-string-literal for more information) repeatedly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.03%. Comparing base (0389ba3) to head (4659b1b).
Report is 11 commits behind head on development.

Additional details and impacted files

@@               Coverage Diff               @@
##           development    #2261      +/-   ##
===============================================
+ Coverage        71.01%   71.03%   +0.01%     
===============================================
  Files              335      335              
  Lines            28820    28820              
  Branches          2527     2527              
===============================================
+ Hits             20466    20471       +5     
+ Misses            8213     8208       -5     
  Partials           141      141              

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.