sortFixturesByDependency silently fails due to CLI filename-based fixture naming mismatch

Describe the bug
When running fixtures via CLI (db load-fixtures), the fixture loader assigns fixture names based on their filenames (e.g., smsMessage.fixture). If a dependent fixture lists short names in dependsOn() (e.g., ['smsMessage']), the strict equality check in sortFixturesByDependency fails to find the dependency and silently falls back to alphabetical execution order without throwing an unhandled dependency error.

Steps to Reproduce

Create a data source fixture smsMessage.fixture.ts.

Create a dependent read model fixture conversation.fixture.ts with dependsOn: () => ['smsMessage'] (or dependsOn: () => ['smsMessage.fixture'] when using defineFixture name overrides).

Run db load-fixtures via CLI.

Observe the execution log order.

Expected Behavior

The CLI loader should either respect explicit name properties inside defineFixture({ name: 'smsMessage' }) or strip the .fixture extension when resolving dependency graph keys.

If a dependency listed in dependsOn() cannot be matched against any registered fixture name, sortFixturesByDependency should throw an explicit error (e.g., Dependency "smsMessage" not found for fixture "conversation"), rather than silently skipping the node and falling back to alphabetical execution order.

Actual Behavior

The CLI loader registers the fixture as smsMessage.fixture.

depends-handler.ts executes fixtures.find((_fixture) => _fixture.name === dependency).

Evaluation 'smsMessage.fixture' === 'smsMessage' returns false, resulting in undefined.

The dependency resolution silently fails, pushing conversation.fixture to run prematurely (alphabetically on 'C' before 'S' and 'T').

Downstream read models query empty collection tables and insert 0 documents.

Environment

Core Package: @antify/database

CLI Command: db load-fixtures

Start with the db load-fixtures command and inspect depends-handler.ts, especially sortFixturesByDependency and its fixture-name comparison. Reproduce the mismatch with smsMessage.fixture and conversation.fixture; done means dependencies resolve using the intended names or an unmatched dependency produces an explicit error instead of alphabetical execution.