We configured Flyway to ignore missing migrations to be able to remove old migrations file (or buggy ones).
So we configure it like ` flyway.ignore-migration-patterns: "*:missing"` which replace the default of `flyway. ignore-migration-patterns: "*:future"`.

So "future" migrations now trigger an error.

We should be able to configure it with ` flyway.ignore-migration-patterns: "*:missing,*:future"` to ignore both missing and future migrations. We can also propose an option to repare the schema but un-supervised this can be dangerous.
flyway migration for version rollback
If people downgrade kesta and there is some migration on the latest version, the user can start the server and will receive this breaking error: 
```
2023-06-12 10:31:03 Caused by: org.flywaydb.core.api.exception.FlywayValidateException: Validate failed: Migrations have failed validation
2023-06-12 10:31:03 Detected applied migration not resolved locally: 14.
2023-06-12 10:31:03 If you removed this migration intentionally, run repair to mark the migration as deleted.
2023-06-12 10:31:03 Need more flexibility with validation rules? Learn more: https://rd.gt/3AbJUZE
```
Define a proper path for downgrading:
- the best transparently
- if not possible, add some tooling to help 
- if not possible, document how to do it  

cli/src/main/resources/application.yml
cli/src/main/resources/application.yml
jdbc-postgres/src/test/resources/application.yml
diff --git a/cli/src/main/resources/application.yml b/cli/src/main/resources/application.yml
index 32731072ae..7d3ceb27aa 100644
--- a/cli/src/main/resources/application.yml
+++ b/cli/src/main/resources/application.yml
@@ -58,7 +58,7 @@ flyway:
       locations:
         - classpath:migrations/postgres
       # We must ignore missing migrations as a V6 wrong migration was created and replaced by the V11
-      ignore-migration-patterns: "*:missing"
+      ignore-migration-patterns: "*:missing,*:future"
     mysql:
       enabled: true
       locations:
@@ -68,7 +68,7 @@ flyway:
       locations:
         - classpath:migrations/h2
       # We must ignore missing migrations as a V8 wrong migration was created and replaced by the V11
-      ignore-migration-patterns: "*:missing"
+      ignore-migration-patterns: "*:missing,*:future"
 
 kestra:
   retries:

diff --git a/jdbc-postgres/src/test/resources/application.yml b/jdbc-postgres/src/test/resources/application.yml
index 6f9f61c0af..db3f240d1d 100644
--- a/jdbc-postgres/src/test/resources/application.yml
+++ b/jdbc-postgres/src/test/resources/application.yml
@@ -13,7 +13,7 @@ flyway:
       locations:
         - classpath:migrations/postgres
       # We must ignore missing migrations as a V6 wrong migration was created and replaced by the V11
-      ignore-migration-patterns: "*:missing"
+      ignore-migration-patterns: "*:missing,*:future"
 
 kestra:
   queue:
