2.0.4

Start against a database the enterprise overlay has migrated (#27)

The overlay ships its own migrations for its own tables. Once one has run,
the history table records a version the open source build has no file
for, and Flyway's default answer to that is to refuse to start:

    Detected applied migration not resolved locally: 20260908203708.

That strands anyone whose enterprise trial ended, and anyone pointing both
editions at one local database — both editions default to the same
database name on the same port.

Flyway now ignores applied migrations this build does not own, both the
"missing" kind (older than its newest migration) and the "future" kind
(newer than anything it has); naming a pattern replaces Flyway's default
of ignoring future ones, so both are listed. Nothing is lost by it: an
overlay migration only ever touches overlay tables, which this edition
never reads. A changed checksum or a failed migration still fails
validation as before, and the test proves both halves.

Signed-off-by: Josh <ascetik@gmail.com>