feat: add new RemoveDownMethodFromMigrations as an opt-in rule for removing the down method's of migration

[joshdonnell]

As someone who always removes the down() method, I felt this rule could be useful as an opt-in alternative to publishing custom migration stubs via Artisan — with the same end result.

It removes the down() method and its docblock comment from migration files.

Enable it by adding:

->withRules([
    RemoveDownMethodFromMigrationsRector::class,
]);

[peterfox]

Thanks @joshdonnell . Is there much value in this over just publishing the stubs and then removing the down method from them compared to having a rule in place?

[FrameworkJosh]

re much value in this over just publishing the stubs and then removing the down method from them compared to having a rule in place?

Thank you for the reply, I believe there is initially what made me create the PR was my dev team members kept asking for something that would automatically remove the down methods for them as we where already using rector it made more sense than adding to Pint for example. I get that you can modify the stubs but I think having this in rector feels more aligned tooling wise for me personally.