Reduce thread yield

[zhiyan114]

Cut down "IO wait" time on main game thread.

Still doesnt resolve the random crash issue smh

[sentry]

Bug: Rapidly pressing the confirm button queues multiple actions. The sequential processing of these actions causes the result screen to be immediately overwritten by the new game screen.
_{Severity: HIGH}

Suggested Fix

To prevent this, consider clearing the action queue after a significant state transition. For example, after processing an action that moves the game from STATE_PLAYING to STATE_OVER_LOST/STATE_OVER_WIN, call xQueueReset(actionQueue) to discard any stale, queued-up actions. Alternatively, add a state check before sending actions to the queue, or introduce a short delay or a "cooldown" state after showing the result screen to prevent immediate restarts.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/main.c#L28-L38

Potential issue: Due to the use of an action queue with a capacity of 8 and non-blocking
sends from button callbacks, rapid presses of the confirm button can queue multiple
`Action_Confirm` events. The `queueHandle` task processes these sequentially. The first
event triggers `confirm_choice()`, which displays the result screen and sets the state
to `STATE_OVER_LOST` or `STATE_OVER_WIN`. The loop immediately processes the next queued
`Action_Confirm`, which then calls `start_game()` based on the new state. This
overwrites the result screen with a new game screen, making the result screen flash for
only a few milliseconds or not appear at all.