Remove unnecessary setTimeout in useExecuteWPCLI hook code block

[sejas]

Related to #214

Proposed Changes

• Remove unnecessary timeout that was added to fake the execution time

Sometimes I was receiving an error even the code block was executed correctly. It's hard to replicate and I think it could be related to this overlooked timeout.

Testing Instructions

• Run Studio with the assistant
• Open the assistant tab
• Send a message to return a wp-cli command, like "generate 10 fake posts"
• Click run
• Observe the code block is still working as expected

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[dcalhoun]

I recently encountered this timeout and wondered why it existed. 😅

When performing the test plan, I encountered an odd success output where the incomplete progress indicator remained in place. Do you think the timeout was in place to ensure the correct output was captured and displayed? Is there an alternative to a timeout that might address this?

If we do remove the timeout, would you be willing to update the recently merged Assistant code block tests to remove the now unnecessary fake timers? We may need to still await the promise resolution via await new Promise( process.nextTick ) or some other mechanism.

[sejas]

I've updated the tests removing the unnecessary useFakeTimers. src/hooks/tests/use-assistant.test.ts is still using it, but for a different timeout.

[katinthehatsite]

The changes look good and the code block still works expected for me 👍

I don't recollect if the horizontal scrolling is supposed to be present in the generated code block once the command runs but that issue is not related to the changes in this PR: