Fix TypeScript error: correct consoleReplay parameter order

Fixes build failures in Lint JS and Ruby and all Pro package builds.

Problem:
- Previous commit had parameters backwards
- consoleReplay signature: (numberOfMessagesToSkip, customConsoleHistory)
- I incorrectly called: consoleReplay(consoleHistory, previouslyReplayedConsoleMessages)
- TypeScript error: Array type not assignable to number parameter

Solution:
- Swap parameters to match signature: consoleReplay(previouslyReplayedConsoleMessages, consoleHistory)
- This is IDENTICAL to the original code before all my "fixes"
- Original code was actually correct all along!

Key Insight:
- The original code's only issue was using consoleReplay instead of buildConsoleReplay
- But the parameter order was already correct
- My first fix changed to buildConsoleReplay (wrapped version - wrong)
- My second fix changed to consoleReplay but swapped params (wrong)
- This third fix uses consoleReplay with ORIGINAL param order (correct!)

Testing:
- TypeScript compilation should now pass
- Pro integration tests should pass
- Console logging tests should pass

References:
- consoleReplay: packages/react-on-rails/src/buildConsoleReplay.ts:18-20

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: justin808

packages/react-on-rails-pro/src/streamingUtils.ts

@@ -112,7 +112,7 @@ export const transformRenderStreamChunksToResultObject = (renderState: StreamRen
   const transformStream = new PassThrough({
     transform(chunk: Buffer, _, callback) {
       const htmlChunk = chunk.toString();
-      const consoleReplayScript = consoleReplay(consoleHistory, previouslyReplayedConsoleMessages);
+      const consoleReplayScript = consoleReplay(previouslyReplayedConsoleMessages, consoleHistory);
       previouslyReplayedConsoleMessages = consoleHistory?.length || 0;
       const jsonChunk = JSON.stringify(createResultObject(htmlChunk, consoleReplayScript, renderState));
       this.push(`${jsonChunk}\n`);