Make it easy to migrate database schema

[rija]

User story

As a developer
I want to be able to upgrade the database schema for new migrations independently from resetting database
So that I can upgrade the schema for a running database (like the one on live production)

Acceptance criteria

Given there is a new migration file merged with schema changes
When the Gitlab pipeline is run
Then I should see a new operational job to run the migration on existing database

Additional Info

At the moment, the migrations are executed when databaseReset is run.
We still want that to happen, but we also want to be able to run them separately.
Mostly because we cannot run databaseReset on live production, and it's better for the operation to be visible
an controllable on the Gitlab pipeline.

Product Backlog Item Ready Checklist

• Business value is clearly articulated
• Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
• Dependencies are identified and no external dependencies would block this item from being completed
• At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
• This item is estimated and small enough to comfortably be completed in one sprint
• Acceptance criteria are clear and testable
• Performance criteria, if any, are defined and testable
• The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

• Item(s) in increment pass all Acceptance Criteria
• Code is refactored to best practices and coding standards
• Documentation is updated as needed
• Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
• No deviation from the team technology stack and software architecture has been introduced
• The product is in a releasable state (i.e. the increment has not broken anything)