Feature Request: Add routeSettings, transitionBuilder and navigatorKey Parameters to Dialog Methods

[codermuss]

Description:
It would be beneficial if showDialog, showCustomDialog, and related methods provided additional parameters to enhance customization options:

•	RouteSettings? routeSettings
•	GlobalKey<NavigatorState>? navigatorKey
•	RouteTransitionsBuilder? transitionBuilder,

Use Case:
These parameters would allow:

•	Custom Routing: routeSettings would enable setting a name and arguments for the dialog’s route, which can assist in analytics and tracking.
•	Navigator Targeting: navigatorKey would provide flexibility to show dialogs in specific navigator instances, which is helpful in applications with multiple navigators or nested navigation.
•	Custom Transitions: transitionBuilder would allow for custom transition animations when displaying dialogs. This is useful for creating a unique user experience or matching the dialog transitions with the app’s design style.

Example image for routing log:
The first line is without routeSettings parameter. The second line is with routeSettings parameter.

[FilledStacks]

This is a really cool PR man!

Thank you. I really like the transition on the custom dialog.

Thanks

[FilledStacks]

🎉 This PR is included in version 1.6.0 🎉

The release is available on:

• v1.6.0
• GitHub release

Your semantic-release bot 📦🚀