When encountering an unexpected error, Sandworm now asks users to submit a crash report.

This happens only in interactive envs (process.stdin.isTTY).

ℹ️ A new Error subclass has been added: UsageError. Usage errors are "expected", related to setup/usage, and do not trigger the crash report process.

Testing it out:

• add a throw somewhere in the code
• try each option in the select
• reports should be visible in our sandworm-audit project, in the production env
• try running it in a dir without a manifest file, to verify that usage errors don't trigger the prompt

Closes #75