Add capability to register database migration from the application/module layer

[shuse2]

Expected behavior

Expect Application class to expose a method called registerMigrations in order to allow applications to define migrations to be run along with the framework migrations.

Also, each module should be able to define its own migrations through the migrations attribute in the module class. By doing so, all chain related migrations should be moved to ChainModule class and all p2p related migrations should be moved to NetworkModule class.

Migrations should be handled by the Controller which will [before loading the modules] get all registered migrations files, order them by date/time and execute the ones not yet executed.

The migration name convention should follow the convention formerly used by Lisk Core: yyyyMMddHHmmss_name_of_migration.sql

Actual behavior

Migrations are handled by Chain Module

Parent

#3146

Which version(s) does this affect? (Environment, OS, etc...)

2.2.0