Replace `ModernHttpRequesterMock` with MockWebServer

[shubham1g5]

Currently we use ModernHttpRequesterMock in unit tests to test out the http requests. We should replace this with OkHttp MockWebServer in order to make tests more dependable by relying on an universal mock library rather than something that we setup in our tests. This will allow us to test network requests directly with okHTTP layer which is the ultimate source of truth for us for network requests.

[github-actions]

🤖 This is an automated response from Test Improver.

Looking at the current ModernHttpRequesterMock implementation, a MockWebServer migration would address a concrete test reliability issue beyond just test realism:

Static state problem: ModernHttpRequesterMock uses four static fields (responseCodeStack, expectedUrlStack, requestPayloadStack, isAuthenticated). If a test fails midway without clearing these stacks, the state leaks into subsequent tests in the same JVM run. MockWebServer's per-instance design avoids this entirely.

Current usage: 6 test files depend on ModernHttpRequesterMock:

• DataPullTaskTest.java
• PostRequestActivityTest.java
• QueryRequestActivityTest.java
• UpdateWorkerTest.kt
• LazyMediaDownloadTest.kt
• AppUpdateTest.kt

Suggested migration approach: Replacing all 6 at once is a large change. A file-by-file migration (one PR per test class) would keep reviews manageable and let CI validate each step independently. PostRequestActivityTest and QueryRequestActivityTest look like natural starting points — they test specific HTTP interactions and don't require the full app initialization that DataPullTaskTest does.

I can prototype the migration for one test class if that would help move this forward.

Generated by Daily Test Improver · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/daily-test-improver.md@346204513ecfa08b81566450d7d599556807389f