feat: Add silent option to checkHotkey to suppress console output

[solssak]

🎯 Changes

This PR adds a silent option to the checkHotkey() function to suppress console output in production environments.
Motivation:
Currently, checkHotkey() always logs validation warnings and errors to the console with no way to suppress them. This can clutter production logs, and developers have no control over this behavior.
What changed:

• Added optional options parameter to checkHotkey() with a silent boolean property
• When silent: true, console.warn() and console.error() calls are suppressed
• Updated JSDoc documentation with usage examples
• Added 3 comprehensive tests to verify the silent option works correctly
  API Example:
  // Before (still works - backward compatible)
  checkHotkey(Alt+C) // Logs to console
  // New option
  checkHotkey(Alt+C, { silent: true }) // No console output
  Testing:
• ✅ All 161 tests pass (including 3 new tests for silent option)
• ✅ Type checking passes
• ✅ Fully backward compatible (no breaking changes)

✅ Checklist

• I have followed the steps in the Contributing guide (https://github.com/TanStack/keys/blob/main/CONTRIBUTING.md).
• I have tested this code locally with pnpm test:lib.

🚀 Release Impact

• This change affects published code, and I have generated a changeset (https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md).
• This change is docs/CI/dev-only (no release).

[KevinVandy]

More than likely, we'll follow the same patterns of tanstack table where we only log in process.env.NODE_ENV === 'production' And we'll also have debug options. So no logs in production. And more opt-in logging on top of some of the default warn/error logs in development

[solssak]

@KevinVandy

Thanks for the feedback! That makes a lot of sense — having a consistent logging strategy with process.env.NODE_ENV guards and opt-in debug options sounds much better than a per-call silent flag.

I'll close this PR for now and take some time to study how TanStack Table handles logging. Happy to contribute again once I have a better understanding of the patterns you're aiming for.