Rename DbScripts_future to DbScripts_finalization (#177)

* Rename DbScripts_future to DbScripts_finalization

* Linting

docs/contributing/database-migrations/index.md

@@ -50,9 +50,9 @@ required.
 3. Write a new Migration and place it in `src/Migrator/DbScripts_finalization`. Name it
    `YYYY-0M-FinalizationMigration.sql`.
    - Typically migrations are designed to be run in sequence. However since the migrations in
-     DbScripts_future can be run out of order, care must be taken to ensure they remain compatible
-     with the changes to DbScripts. In order to achieve this we only keep a single migration, which
-     executes all backwards incompatible schema changes.
+     DbScripts_finalization can be run out of order, care must be taken to ensure they remain
+     compatible with the changes to DbScripts. In order to achieve this we only keep a single
+     migration, which executes all backwards incompatible schema changes.
 
 ### EF migrations