Fix StripeException#getUserMessage on v1 API errors

[jar-stripe]

Why?

This issue #1899 reports that CardException#getUserMessage() returns null after upgrading to SDK v27.1. The root cause is that the underlying StripeError#getUserMessage is only valid for v2 errors. Because it is not present on v1 errors, it will be null in the StripeError object. This PR fixes the issue by ensuring we only access the user message in StripeError for v2 errors.

What

• Adds stripeErrorApiMode internal field to StripeException to store which API version returned the error
• Adds setStripeV2Error method to set the error and set the stripeErrorApiMode to V2; modified setStripeError to set the stripeErrorApiMode to V1
• Modifies StripeException getUserMessage to return error.getMessage() if we've wrapped a v1 error
• Modifies StripeException getMessage to not include user message if we've wrapped a v1 error
• Adds unit tests for setting v1 and v2 errors in StripeException

Changelog

• Fix StripeError#getUserMessage to return getMessage for errors returned from v1 API calls. This matches pre-v27 behavior for v1 API errors.

[jar-stripe]

I was able to reproduce the issue and then validate the fix with:

try {
  PaymentIntentCreateParams params =
      PaymentIntentCreateParams.builder()
          .setCurrency("usd")
          .setAmount(2000L)
          .setConfirm(true)
          .setAutomaticPaymentMethods(
              PaymentIntentCreateParams.AutomaticPaymentMethods.builder()
                  .setAllowRedirects(
                      PaymentIntentCreateParams.AutomaticPaymentMethods.AllowRedirects.NEVER)
                  .setEnabled(true)
                  .build())
          .setPaymentMethod("pm_card_chargeDeclinedProcessingError")
          .build();
  StripeClient client = new StripeClient(this.apiKey);
  PaymentIntent paymentIntent = client.paymentIntents().create(params);
  System.out.println("PaymentIntent created: " + paymentIntent);
} catch (StripeException e) {
  e.printStackTrace();
  System.out.println(e.getUserMessage());
}