IBX-11939: Fix tagged migrations breaking when enable_service_migrations is false

[Steveb-p]

🎫 Issue	IBX-11939

Related PRs:

• IBX-11939: [Doctrine Migrations] Added Doctrine Migrations-based schema and data install path (inlined SQL) core#785

Description:

RegisterMigrationsPass bound every IbexaMigrationTag-tagged migration's Connection/LoggerInterface constructor arguments to DoctrineMigrationsBundle's doctrine.migrations.connection/doctrine.migrations.logger services. Those two services are removed from the container entirely by DoctrineMigrationsExtension::load() when enable_service_migrations is false, so any tagged migration (e.g. ibexa/core's InstallSchemaMigration) made container compilation fail with:

The service "..." has a dependency on a non-existent service "doctrine.migrations.logger".

for any project not explicitly enabling that flag. Found while investigating a Behat CI failure on ibexa/core#785 — InstallSchemaMigration extends Doctrine\Migrations\AbstractMigration, whose constructor requires both a Connection and a LoggerInterface, so this wasn't an optional convenience binding.

Fix: both are now sourced from the application's own doctrine.migrations.dependency_factory (registered unconditionally by DoctrineMigrationsBundle regardless of enable_service_migrations) via two new Ibexa-owned services — ibexa.doctrine_migrations.connection and ibexa.doctrine_migrations.logger — rather than DoctrineMigrationsBundle's own aliases. doctrine.* service IDs belong to that bundle, not to Ibexa, to redefine.

[Steveb-p]

5.0 tier: #5