fix(@inquirer/core): clear hook effects before settling prompts - #2255

Characterize how a prompt settles when a useEffect cleanup throws:
the prompt rejects with the cleanup error, and the answer (or the
original settlement error, e.g. AbortPromptError) is dropped.

These tests pass on current main; they guard the existing settlement
semantics against regressions while the settlement path is reworked in
the next commit.

createPrompt cleared hook effects only after the prompt promise settled,
in a microtask. But readline emits keypresses synchronously within a
single data event, so input batched with the key that settled the prompt
still reached useKeypress handlers before cleanup ran.

Clear hook effects in the synchronous settlement path instead:
- resolve: clear effects, then resolve
- reject/cancel/abort: clear effects, then reject

The interface cleanup (screen.done + output.end) still runs in finally,
so it happens after the prompt reaches its done state. As a side effect,
prompts created with an already-aborted signal now also run the terminal
cleanup instead of leaking the readline interface.

The settlement path is kept minimal: the promise resolvers and
effectScheduler.clearAll() are both idempotent, so no settled guard is
needed; the bound cleanup is named clearEffects to avoid shadowing the
hook-engine store field name.

Event listener registrations go through a listenTo() helper returning
the disposer, so each site collapses into a single
cleanups.add(listenTo(...)) statement.

Adds regression coverage for the done, abort, cancel, and
already-aborted signal settlement paths.

Closes SBoudrias#1816

Co-authored-by: Joel Towell <156634308+JoelTowell@users.noreply.github.com>