CMR-9895: Add new integration test group

[jmaeng72]

Overview

What is the feature/fix?

Integration tests take about 94+ mins to run during CMR builds

What is the Solution?

Took half of the search tests and added it to a new integration test group to run in parallel with the others

What areas of the application does this impact?

CMR Core build. But no logic.

Checklist

• [ ] I have updated/added unit and integration tests that prove my fix is effective or that my feature works
• [ ] New and existing unit and int tests pass locally and remotely with my changes
• [ ] I have removed unnecessary/dead code and imports in files I have changed
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have cleaned up integration tests by doing one or more of the following:
  • de-duped, consolidated, removed dead int tests
  • transformed applicable int tests into unit tests
  • refactored to reduce number of system state resets by updating fixtures (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 :white_check_mark:

Project coverage is 56.54%. Comparing base (d3a9ce3) to head (b8070b9). Report is 1 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #2114 +/- ## ========================================== - Coverage 57.81% 56.54% -1.28% ========================================== Files 1044 1044 Lines 70311 70311 Branches 1967 1977 +10 ========================================== - Hits 40649 39756 -893 - Misses 27807 28670 +863 - Partials 1855 1885 +30 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.