Fix: Resolve duplicate loop operations in TestCaseRepository

[aniruddhaadak80]

Resolves issue #27060. The loop calling deleteChildren was incorrectly placed inside another loop, turning an O(N) deletion operation to O(N^2) against testcases. Also removes redundant AsyncExecutor deletion block

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[gitar-bot]

Code Review ✅ Approved

Refactored TestCaseRepository to eliminate O(N^2) duplication, improving overall data processing efficiency. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[Copilot]

Pull request overview

This PR fixes an inefficient deletion path in the backend TestCaseRepository that caused redundant (O(N²)) deletions of TestCaseResolutionStatus children and also removed a duplicate deletion of test case results that was executed both synchronously and asynchronously.

Changes:

• Fix deleteChildren() to perform a single pass over child records (O(N)) and instantiate the TestCaseResolutionStatusRepository once.
• Remove the redundant async deletion block in deleteAllTestCaseResults() and delete exactly once.
• Remove the now-unused ExecutorService/Executors field and imports.

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!