Allow explicit Doctrine transport factory configuration

[f3l1x]

Summary

This change allows the Doctrine transport factory to be explicitly configured via NEON configuration, while preventing automatic registration when a custom definition is already provided.

Key Changes

• Added DummyConnectionRegistry mock class for testing Doctrine transport factory registration
• Modified TransportFactoryPass to check if a Doctrine transport factory definition already exists before auto-registering one
• Added test case verifying that explicitly configured Doctrine transport factory is properly registered

Implementation Details

The fix prevents duplicate Doctrine transport factory registrations by checking hasDefinition() before adding the auto-wired definition. This allows users to explicitly define their own messenger.transportFactory.doctrine service in configuration without conflicts, while maintaining backward compatibility with automatic registration when no explicit configuration is provided.

https://claude.ai/code/session_015tqPb45KBUxcxpsePPSCYG

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.90%. Comparing base (ca5a43d) to head (6ae75b6).

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   95.90%   95.90%           
=======================================
  Files          26       26           
  Lines         659      659           
=======================================
  Hits          632      632           
  Misses         27       27           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.