Implemented Module Migration Feature

[nitinsinghoxidesales]

Implemented Module Migration Feature

Note: Currently we are implementing this feature with PS oxid-console module and later we will merge this feature with core console module.

[alfredbez]

The following things should be tested in CI:

• still runs migrations from the project only
• runs migrations from active modules
• does not run migrations from inactive modules
• runs migrations from the project and from modules in a single run
• does not run migrations from active modules if --skip-module-migration is set
• works with OXID 6.1
• works with OXID 6.2

[nitinsinghoxidesales]

All the check points been tested on my local system and its working for me. I just have to test whether it works with OXID 6.1 or not.

[alfredbez]

I'd like to have these checks in a CI system like Github Actions.

[nitinsinghoxidesales]

Sure, i will add all these checks with github checkpoints.

[alfredbez]

It would also be helpful if we display the migration-directories in the output, e.g.:

Running migration scripts
adding migrations from <module-id1 / module-path1>
adding migrations from <module-id2 / module-path2>
Migration finished successfully

[keywan-ghadami]

related work from the oxid core team: OXID-eSales/oxideshop-facts@383a33c

[nitinsinghoxidesales]

@keywan-ghadami
FYI - Seems there is an error with recent changes in OXID-eSales/oxideshop-facts@383a33c package.

Here is my comment.
OXID-eSales/oxideshop-facts@383a33c#r39852749