UVE: Improve test runner

Parent Issue

No response

Task

The UVE portlet currently has a large number of unit tests.
However, running them takes significantly longer compared to other test runners.

For other tests, execution starts immediately, even if the tests themselves take time to complete.

In the case of UVE, the tests take around 5 minutes just to start running.

Sometimes, they never start executing, requiring a manual restart of the process.
Other times, they start but never progress or complete, forcing another restart.
This issue needs investigation—there may be a misconfiguration in Jest for this portlet. While a long execution time is expected due to the number of tests, the excessive delay in starting suggests a deeper problem beyond just test volume.

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

Acceptance Criteria

No response

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Start by reproducing the UVE portlet test runner behavior and inspecting its Jest configuration, then compare startup behavior with the other test runners. Done means the tests begin reliably without a five-minute delay, hanging, or requiring a manual process restart.