[NFR]: Move MVC event names from collectors to an MVC bridge #15

Summary

Collectors hold framework event names in their subscribe() methods. Move these names to one bridge that calls the collector push methods from #44. MVC behavior does not change.

ADR does not depend on this issue. It is a cleanup, so that a collector has no framework event names.

Current coupling

• DatabaseCollector → db:beforeQuery, db:afterQuery
• ViewCollector → view:beforeRenderView, view:afterRenderView
• RouteCollector → router:matchedRoute
• ExceptionsCollector → dispatch:beforeException
• CacheCollector → cache:afterGet, cache:afterSet, cache:afterHas, cache:afterDelete

Proposed direction

• Add an MVC bridge that attaches these listeners and calls the push methods. Provider boots it.
• The typed push methods are the canonical signal set. Do not add a separate signal vocabulary or event bus. This replaces the three layers in the earlier text of this issue, and needs less code.
• Keep the Subscriber contract and the subscription loop for third-party collectors. Built-in collectors stop implementing it.
• view:* and cache:* also fire outside MVC. Put these listeners in a part that the ADR bridge can use also.
• The bridge gives RouteCollector a callable that reads the MVC router at collect time (see [NFR]: Add a direct push API to collectors #44).

Acceptance

• Built-in collectors have no framework event names.
• A collector gets data with no events manager.
• The MVC bridge keeps the current behavior (as used by phalcon/vokuro). Existing subscribe() tests move to the bridge with the same assertions.
• Tests pass with full coverage. phpcs and phpstan pass.
• RouteCollector has no Phalcon\Mvc imports.

Depends on

• Slice 2 [NFR]: Extract a neutral boot core from Provider #40
• Slice 7 [NFR]: Add a direct push API to collectors #44

Part of

#13