[PRImpl] Invalid PaymentRequestDetails should cause CPRImpl discardment

Fix a bug introduced from CL https://chromium-review.googlesource.com/c/chromium/src/+/2346730
where the failed parseAndValidateDetailsOrDisconnectFromClient() does
not cause the ComponentPaymentRequestImpl to be discarded by the
MojoPaymentRequestGateKeeper.

Bug: 1102522

Change-Id: I0b99b6aea2ada05e5a0474e3cb93eaed9a4ee789
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363249Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799141}

chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentRequestImpl.java

@@ -434,7 +434,7 @@ public class PaymentRequestImpl
             mQueryForQuota.put("basic-card-payment-options", paymentMethodData);
         }
 
-        if (!parseAndValidateDetailsOrDisconnectFromClient(details)) return true;
+        if (!parseAndValidateDetailsOrDisconnectFromClient(details)) return false;
         mSpec = new PaymentRequestSpec(mPaymentOptions, details, mMethodData.values(),
                 LocaleUtils.getDefaultLocaleString());