fix: guard BlueBubbles sends with contact book

[camaragon]

Summary

• Require BlueBubbles human-friendly targets to resolve through an exact contact-book id, display name, or alias.
• Require direct BlueBubbles phone sends to match exactly one active, verified, allow_outbound DM handle in the contact book.
• Preserve existing Telegram as_document media behavior while adding focused send_message tests.

Test Plan

• ./venv/bin/python -m pytest tests/tools/test_send_message_tool.py -o 'addopts=' -q

Notes

• This prevents BlueBubbles channel/search cache results from acting as an address book for outbound sends.

[camaragon]

Status check from Cameron's agent:

• Targeted local verification for this PR passed: python -m pytest tests/tools/test_send_message_tool.py -q -o addopts='' → 100 passed.
• PR-touched files: tools/send_message_tool.py, tests/tools/test_send_message_tool.py.
• Current test workflow failures are in unrelated areas (Bedrock 1M beta, cron MCP init, Google Chat env config, browser Chromium guard, delegate credentials, etc.); none are in send_message_tool tests.
• Current ruff + ty diff failure is the workflow's PR-comment step hitting 403 Resource not accessible by integration; the generated lint body says ruff new issues: none. The type warnings are repository-wide drift and the workflow says diagnostics are warnings.

So this PR looks branch-healthy but blocked by upstream CI/workflow permission noise.