fix(tests): apply linter formatting and use optional chaining

Fix linting violations that were preventing CI from passing:

1. test/argv/parse.test.ts:
   - Use optional chaining with type assertion to satisfy both linter
     and TypeScript type checker
   - Cast result.raw['--'] to string[] | undefined before using ?.includes()
   - Wrap in Boolean() for explicit type conversion
   - Apply multi-line formatting for readability

2. test/performance.test.ts:
   - Collapse multi-line it() function to single line as per formatter
   - Maintain retry logic and comments

Both changes preserve functionality while meeting code style requirements.

Author: jdalton

test/argv/parse.test.ts

@@ -155,7 +155,9 @@ describe('argv/parse', () => {
       // Arguments after -- may be in positionals or in the raw['--'] array
       const hasFlag =
         result.positionals.includes('--not-a-flag') ||
-        (result.raw['--'] && result.raw['--'].includes('--not-a-flag'))
+        Boolean(
+          (result.raw['--'] as string[] | undefined)?.includes('--not-a-flag'),
+        )
       expect(hasFlag).toBe(true)
     })
 

test/performance.test.ts

@@ -20,20 +20,16 @@ describe('performance', () => {
   })
 
   describe('basic performance measurements', () => {
-    it(
-      'should measure elapsed time',
-      { retry: 3 },
-      async () => {
-        const start = performance.now()
-        await new Promise(resolve => setTimeout(resolve, 10))
-        const end = performance.now()
-        const elapsed = end - start
-        expect(elapsed).toBeGreaterThan(0)
-        // Allow for timer imprecision (9ms threshold instead of 10ms)
-        // setTimeout is not guaranteed to be exact due to OS scheduling
-        expect(elapsed).toBeGreaterThanOrEqual(9)
-      },
-    )
+    it('should measure elapsed time', { retry: 3 }, async () => {
+      const start = performance.now()
+      await new Promise(resolve => setTimeout(resolve, 10))
+      const end = performance.now()
+      const elapsed = end - start
+      expect(elapsed).toBeGreaterThan(0)
+      // Allow for timer imprecision (9ms threshold instead of 10ms)
+      // setTimeout is not guaranteed to be exact due to OS scheduling
+      expect(elapsed).toBeGreaterThanOrEqual(9)
+    })
 
     it('should support performance.now()', () => {
       const now = performance.now()