IBX-12530: Rebuilt DatabaseSchemaHook on SchemaBuilderInterface instead of a raw-file reimplementation

[Steveb-p]

🎫 Issue	IBX-12530

Description:

DatabaseSchemaHook used to import raw schema.yaml files (listed via SchemaFilesProviderInterface) through LegacySchemaImporter — a test-only importer that never dispatches SchemaBuilderEvent. So any package contributing its schema through that event rather than a schema.yaml (e.g. deriving it from Doctrine ORM mappings via SchemaTool) was never exercised by integration tests at all, even though the event is exactly what ibexa:install's legacy path relies on in production.

It now calls SchemaBuilderInterface::buildSchema() — the same production code — and applies the resulting Schema's SQL directly, since the test database is always freshly created. A test kernel no longer declares which schema files to load: whatever bundles it registers is what the schema contains.

That needs two bundles present: DoctrineSchemaBundle for SchemaBuilderInterface, and IbexaRepositoryInstallerBundle because core's own BuildSchemaSubscriber lives there rather than in IbexaCoreBundle — without it you get every other package's tables but none of core's. Rather than gate the registration, the hook is registered like any other and RemoveUnsatisfiableHooksPass drops it when either collaborator is absent. It checks for the services themselves (SchemaBuilderInterface, and RepositoryInstaller's BuildSchemaSubscriber) rather than for bundle names, and runs at the default compiler-pass priority — before AutowirePass, so removing the definition beats autowiring failing on it.

SchemaFilesProviderInterface and the rest of that chain (SchemaFilesKernelMethodProvider, SchemaFilesParameterProvider, SchemaFilesProviderChain, and the ibexa.test.schema_files parameter) only ever existed to feed this hook, so they're gone. DefaultSchemaFilesProvider stays: IbexaTestKernel::getSchemaFiles() is still mandated by IbexaTestKernelInterface, and ibexa/core's IbexaKernelTestTrait::loadSchema() reads it when a test calls it explicitly.

Downstream packages each need a small follow-up (register the two bundles, drop their own *SchemaFilesProvider); those land separately. #44 builds on this to let Bootstrapper accept a non-Ibexa kernel, reusing the same pass for the other built-in hooks.

For QA:

Checked against four packages spanning the range of Bootstrapper setups, each with its explicit schema file list removed:

Package	setup	result
ibexa/activity-log	plain bootstrap(), 1 schema file	124 tests, unchanged
ibexa/taxonomy	ORM-derived schema, no schema.yaml at all	34 tests, unchanged
ibexa/cart	3 schema files / 3 bundles, purge-index hook	86 tests, schema byte-identical
ibexa/order-management	5 schema files / 5 bundles, fixtures hook, migrations	163 tests, schema a superset

The order-management difference is worth a look: the event-driven schema additionally contains ibexa_user_invitations and ibexa_user_invitations_assignments (plus indexes and FK). Those come from ibexa/user's subscriber, and IbexaUserBundle is registered in that test kernel — the hand-maintained file list had just never included it. Diff was one-directional in both packages: nothing the file list produced went missing.

Also confirmed the pass behaves both ways: a full kernel keeps all four hooks, and ibexa/doctrine-migrations' minimal kernel (no ibexa/core at all) drops every one of them and still boots.

[konradoboza]

@Steveb-p please create and attach a proper JIRA ticket.