Ensure migrations use the correct configured database connection

[G4b0rDev]

This PR ensures that the migration for Pennant use the configured database connection.

Why is this needed?

Currently, the migration does not explicitly set the database connection, which causes issues when using a custom connection for Pennant. As a result, migrations may run on the default connection instead of the intended one.

How does this fix it?

• Uses getConnection() to ensure the migration runs on the correct database connection.
• Ensures compatibility for multi-database setups.

Let me know if any adjustments are needed.

[taylorotwell]

I would make this migration we publish extend a PennantMigration which is in the package and contains this method and extends the base migration. Then the user never sees this method.

[taylorotwell]

Please mark as ready for review when the requested changes have been made.

[G4b0rDev]

Thank you. I’ve implemented the requested changes.
Should I update the upgrade guidelines to reflect the updated migration extending the new class?

[timacdonald]

@G4b0rDev, I don't think we need to update the docs. We publish the migration, so the user owns it and could make this change locally if they needed.