CMR-11044: Removing system validation test from the CMR.

[eereiter]

Overview

What is the objective?

Removing system-validation-test from the CMR. This code has been moved to bitbucket.

What are the changes?

Removing system-validation-test from the CMR.

What areas of the application does this impact?

system-validation-test

Required Checklist

• New and existing unit and int tests pass locally and remotely
• clj-kondo has been run locally and all errors in changed files are corrected
• I have commented my code, particularly in hard-to-understand areas
• I have made changes to the documentation (if necessary)
• My changes generate no new warnings

Additional Checklist

• I have removed unnecessary/dead code and imports in files I have changed
• I have cleaned up integration tests by doing one or more of the following:
  • migrated any are2 tests to are3 in files I have changed
  • de-duped, consolidated, removed dead int tests
  • transformed applicable int tests into unit tests
  • reduced number of system state resets by updating fixtures. Ex) (use-fixtures :each (ingest/reset-fixture {})) to be :once instead of :each

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.18%. Comparing base (d304270) to head (1028f80).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2450      +/-   ##
==========================================
- Coverage   58.20%   58.18%   -0.02%     
==========================================
  Files        1069     1069              
  Lines       74278    74278              
  Branches     2165     2165              
==========================================
- Hits        43233    43220      -13     
- Misses      29028    29035       +7     
- Partials     2017     2023       +6     

☔ View full report in Codecov by Harness.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.