feat(integrations): bridle and bridle kb are plugpress plugins (#338)

[ifahimreza]

Closes #338. Supersedes #289 (and its issue #288).

Owner, 2026-10-05: "remove saddle-pro knovia; Bridle KB and Bridle are part of Saddle free."

What changes

• Saddle_Integrations::FIRST_PARTY gains bridle and bridle-kb. Both plugins enrol themselves through saddle_integrations (plugpressco/bridle#90, plugpressco/bridle-kb#8); their tools are now live as soon as the plugin is active, like Mailyard and SEO, with no switch under Services. The owner can still turn single tools off under Settings → Advanced.
• integration_prefixes() drops the knovia- floor: Saddle Pro removes its knovia catalog entry (plugpressco/saddle-pro companion PR), and Bridle KB is grouped under Integrations by the live catalog.
• Old names leave Core docblocks (knovia examples → bridle-kb, inbees → bridle). The one remaining knovia- is the test asserting it stays out of the grouping.
• Changelog: a "Changed" line under the drafted 1.5.2 entry (no version bump here).

Tests

• New: test_bridle_and_bridle_kb_are_first_party_and_stay_apart enrols both, checks each is live with nothing approved, labelled PlugPress, and that Bridle's bridle/ prefix counts only its own tool (Bridle KB's bridle-kb/ shares the start).
• test_every_plugpress_plugin_is_first_party pins the two new slugs.
• composer test: 1450 tests OK (1 skipped, as on main). phpcs: no findings on changed lines.

Verified by hand

On the Bridle Studio site (Saddle linked from this checkout) with Bridle and Bridle KB active and saddle_enabled_integrations empty: listing() shows both as plugpress, enabled (Bridle 7 tools, Bridle KB 9), and all 16 saddle/bridle-* wrappers register. The same wrappers were exercised over /wp-json/saddle/v1/mcp earlier the same day (reads, drafts, notes, preview-and-confirm).

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}