fix(daemon): activate tabs before mouse input

[MonkeyLeeT]

Summary

• activate click targets before resolving DOM coordinates or dispatching mouse events
• activate scroll targets before dispatching wheel events
• add daemon dispatch tests covering activation order for click and scroll

Root cause

Chrome can accept Input.dispatchMouseEvent for background targets without producing DOM click or wheel effects. Measuring click coordinates before activation can also use stale background-tab layout, so the target now becomes foreground before coordinate resolution.

Validation

• pnpm --filter @bb-browser/daemon test
• pnpm build
• pnpm lint
• pre-commit hook ran pnpm build and pnpm test

Fixes #144