Consider creating a base Stripe gateway for better code reusability

I'm working on implementing an integration for stripe SEPA and found that a lot of the code in the stripe payment gateway can be inherited except for some cases where credit card specific code is added.
I think there's a case for introducing a new StripeBase payment gateway that handles everything related to the main configuration fields, refunds, creating payments while the subclasses will handle the creation of payment methods based for their specific payment method.
We can also consider adding checks in the stripe review pane for a new ImplementsCreditCard interface instead of the generic StripeInterface.