Fix flaky timing tests on Windows CI

Increase timing margins for Windows CI environment:
- Cache TTL test: 100ms TTL → 200ms, wait times 50ms/75ms → 100ms/120ms
- HTTP timeout test: 500ms timeout → 2000ms (100ms /slow endpoint)

Author: jdalton

test/cache-with-ttl.test.ts

@@ -329,16 +329,16 @@ describe('cache-with-ttl', () => {
 
     it('should refresh TTL on set', async () => {
       const refreshCache = createTtlCache({
-        ttl: 100,
+        ttl: 200,
         prefix: 'refresh-cache',
       })
 
       await refreshCache.set('key', 'value1')
-      await new Promise(resolve => setTimeout(resolve, 50))
+      await new Promise(resolve => setTimeout(resolve, 100))
       await refreshCache.set('key', 'value2') // Refresh TTL
 
-      await new Promise(resolve => setTimeout(resolve, 75))
-      // Should still be cached (50 + 75 = 125ms, but TTL refreshed at 50ms)
+      await new Promise(resolve => setTimeout(resolve, 120))
+      // Should still be cached (100 + 120 = 220ms, but TTL refreshed at 100ms)
       expect(await refreshCache.get<string>('key')).toBe('value2')
 
       await refreshCache.clear()

test/http-request.test.ts

@@ -329,7 +329,7 @@ describe('http-request', () => {
 
     it('should complete before timeout', async () => {
       const response = await httpRequest(`${httpBaseUrl}/slow`, {
-        timeout: 500,
+        timeout: 2000,
       })
       expect(response.text()).toBe('Slow response')
     })