Editing reusable payment methods

The patch here will need to be reworked, since we've decided that PaymentMethodEditForm should not share code with any other forms.
The sprit of the patch in #10 was completed in #2858599: Move a portion of the PaymentInformation pane logic to a PaymentOptionsBuilder

We just need a simple form that edits the billing profile, and a matching gateway method to call.

Here is a rebuilt, minimal patch, allowing only billing profile updates.

It might make sense to also support modifying the expiration date, either in the main form or at least in the one for the Onsite example gateway.

Well, I assumed we wouldn't want to support retokenization, people would add a new payment method for that.
The use cases here are 1) Update the billing info 2) Update the expiration date, when supported (usually supported without PCI implications)

Discussed with bojanz. We identified the following reasons for needing to update a payment method instead of replacing the payment method (retokenizing.)

• The customer's billing information has changed, and AVS validation is performed by the merchant's gateway.
• The card is expired, or near expiration, and the customer has a new expiration date to provide so that payment does not fail.

After reviewing the various payment gateway APIs, it is possible to pass a new expiration date along with a remote payment method ID to update a payment method without full retokenization of the card.

That means we can render the masked credit card number that we already have and just prompt the customer for the expiration date information. I'm resetting the patches back to #15 and we will work from there.

Relevant links for payment gateway APIs:

• Authorize.net: https://developer.authorize.net/api/reference/index.html#customer-profil...
• Stripe: https://stripe.com/docs/api#update_card
• Braintree: https://developers.braintreepayments.com/reference/request/payment-metho...
• Square: does not support updating cards, see https://docs.connect.squareup.com/api/connect/v2#navsection-customers

Also want to update title and issue summary because this feature will be 💯💯💯💯💯💯

Update issue summary.

Here is my update. Allows editing the expiration information. Displays the card type image, updates the payment method's expiring time as well. Then passes it to the payment gateway.

I forgot to update the test.

+++ b/modules/payment/tests/src/Functional/PaymentMethodTest.php
@@ -100,7 +100,35 @@ class PaymentMethodTest extends CommerceBrowserTestBase {
+      'payment_method[payment_details][expiration][year]' => '2026',
...
+    $this->assertSession()->pageTextContains('2/2024');

.. of course it failed.

Here is the updated patch and test.

+      '#template' => '<span class="payment-method-icon payment-method-icon--{{ type }}"></span>Credit card ending in {{ mask }}',

This isn't translatable, no? Can we just use $payment_method->label()? That would give us "Visa ending in 1111"

Yeah, dumb. Too long in client land. That makes more sense.

\o/ Committed!