test(sandbox): drop explicit any from the new conformance stream mocks

The two new E2B mocks annotated their arguments as `any`, which both violates
the repo's no-`any` rule and defeats the point of a mock: an invalid SDK shape
would type-check.

Matches the sibling mock a few lines above (`async (_code, options) =>`) and
infers from the `vi.fn()` signature instead of naming a type, so the mock stays
bound to whatever the adapter actually calls.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: icecrasher321

apps/sim/lib/execution/remote-sandbox/conformance.test.ts

@@ -379,7 +379,7 @@ describe.each(PROVIDERS)('sandbox conformance [%s]', (provider) => {
     // while producing no oversized result — the caller parses every chunk and keeps none of it.
     const oversized = 'x'.repeat(MAX_SANDBOX_PROCESS_OUTPUT_BYTES + 1024)
     if (provider === 'e2b') {
-      mockE2BCommandsRun.mockImplementationOnce(async (_cmd: string, options: any) => {
+      mockE2BCommandsRun.mockImplementationOnce(async (_cmd, options) => {
         options.onStdout(`${oversized}TAIL_MARKER`)
         return { stdout: `${oversized}TAIL_MARKER`, stderr: '', exitCode: 0 }
       })
@@ -416,7 +416,7 @@ describe.each(PROVIDERS)('sandbox conformance [%s]', (provider) => {
   it('still bounds a stream the caller does not consume', async () => {
     const oversized = 'x'.repeat(MAX_SANDBOX_PROCESS_OUTPUT_BYTES + 1)
     if (provider === 'e2b') {
-      mockE2BCommandsRun.mockImplementationOnce(async (_cmd: string, options: any) => {
+      mockE2BCommandsRun.mockImplementationOnce(async (_cmd, options) => {
         options.onStderr(oversized)
       })
     } else {