feat: add useTapAway

[Coooder-Crypto]

Added useTapAway and docs for issue #7

• Implemented background-only useTapAway: listens to GlobalEventEmitter tap events (default bindtap), checks targets via equality/contains/uid/id, and invokes the callback when the tap is outside; exported from src/index.ts.
• Added tests (tests/useTapAway.test.tsx) covering inside/outside taps, cleanup on unmount, and custom event names; all passing locally.
• Added Chinese docs at docs/zh/events/useTapAway.md and linked from the events README.

Type notes: the hook uses a minimal event shape (target/detail.target) instead of MainThread.TouchEvent because it runs in the background and consumes GlobalEventEmitter payloads, which may not match MTS touch events; consumers can supply a narrower type via the generic if needed. Default event name is bindtap; adjust if runtime uses a different tap event.

[gaoachao]

The bindtap event is not being captured by the global GlobalEventEmitter.

[gaoachao]

Hi, @Coooder-Crypto, thanks for your contribution! However, the current implementation doesn't seem to achieve the goal of useTapAway. Here's my proposed solution:

• Set trigger-global-event on the root node to forward tap events to GlobalEventEmitter
• Extract the node path (clicked node → root) using uid from event.target
• Retrieve the target node's uid via ref
• Iterate through the path comparing uids to check if the target node exists in the path; trigger callback if absent

[Coooder-Crypto]

Happy New Year, @gaoachao.

I also want to sincerely apologize first: in my first PR, I started implementing before fully understanding Lynx and the real goal of useTapAway, which increased your review cost. Sorry about that.

After studying Lynx more carefully, I rewrote the implementation. In this version:

• useTapAway is based on GlobalEventEmitter with tap;
• the trigger-global-event forwarding path is aligned;
• inside detection uses a fast path (event.target / uid) plus a path suffix fallback;
• tests and docs were updated accordingly.

One known limitation remains: the third parameter is not a react-use style event array yet (e.g. ['click'] / ['mousedown', 'touchstart']). The current contract is tap-only (default is also tap).

If you prefer, I can follow up in this PR (or a separate PR) with array-shaped compatibility that still maps to tap internally.

BTW, I recently joined ByteDance as a frontend intern. This is my first time implementing a relatively low-level hook, and I’d really like to keep contributing to this repo long-term. Thanks again for your guidance and patient review.