* Remove unused legend

* Add support for bcmc separate component

* Fix google pay

* Add PWA origin for the getRedirectUrl() in the transparent redirect

Add support for PWA dedicated frontend urls per store

* Add query when redirecting to the result controller

* Delete Redirect.php - not used anymore

* Add merchant reference in the return url as get param to support PWA

* Store details in the payment additional information object

* [WIP] use result as a generic handler for redirects

Validate all the redirects via payments/details
Validate the parameters for payments/details with the details list from
the first payments response

* [WIP] use result as a generic handler for redirects

* Update Controller/Process/Result.php
Co-authored-by: Ángel Campos <angel.campos@adyen.com>
Co-authored-by: Ángel Campos <angel.campos@adyen.com>

* Tokenize payment methods in payment response handler

Do not save recurring details "manually" for /payments/details response

* Standardise Oneclick Observer

* Use generic component for recurring payments

* sonarcloud suggestions

* Remove unused div

Release 6.6.7

[PW-3157] [iDeal] First notification is unsuccessful but a second notification 2 minutes later send a success response => order canceled but payment is in success (#910)

* Delay processing of AUTHORISATION success=false notifications by 10 min

In some edge cases (for example 3DS1 authentication) an authorisation
success=false notification can be sent earlier than the success=true one
The reason can be a closed and reopened mobile application where the
customer performs the 3DS1 authentication
To avoid closing false unsuccessful orders, processing authorisation
success=false and offer_closed notifications are delayed

* Simplify date calculations

Add @peterojo to codeowners

# Conflicts:
#	Gateway/Validator/CheckoutResponseValidator.php
#	etc/events.xml
#	view/frontend/web/js/view/payment/method-renderer/adyen-cc-method.js
#	view/frontend/web/js/view/payment/method-renderer/adyen-google-pay-method.js

Co-authored-by: Alexandros Moraitis <alexandros.moraitis@adyen.com>
Co-authored-by: Attila Kiss <42297201+cyattilakiss@users.noreply.github.com>

* Update PaymentLink.php

To avoid "class not found" exception

* [bugfix/896] check array key
Co-authored-by: shakil imran <shakil.imran@monotaro.com>
Co-authored-by: Attila Kiss <42297201+cyattilakiss@users.noreply.github.com>

[PW-3330] Google pay button is enabled only if the terms and conditions are enabled [PW-3526] Show message for Google pay (#892)

* Do not disable google pay button when payment form is valid

Do not disable google pay button when terms and conditions is automatic
or when it is disabled

* Show message for google pay when gateway responds with a message

Co-authored-by: Alessio Zampatti <alessio.zampatti@adyen.com>
Co-authored-by: Attila Kiss <42297201+cyattilakiss@users.noreply.github.com>

Orders paid by alternative payment methods have the state new after
order creation therefore when an authorization success=false
notification is being processed close orders with state new as well not
just the payment_review state ones

Apply getNotificationsCanCancel() for all cases not just when the order
is in payment_review state

Co-authored-by: Attila Kiss <42297201+cyattilakiss@users.noreply.github.com>

* Update PaymentLink.php

To avoid "class not found" exception

* [bugfix/896] check array key
Co-authored-by: shakil imran <shakil.imran@monotaro.com>
Co-authored-by: Attila Kiss <42297201+cyattilakiss@users.noreply.github.com>

[PW-3330] Google pay button is enabled only if the terms and conditions are enabled [PW-3526] Show message for Google pay (#892)

* Do not disable google pay button when payment form is valid

Do not disable google pay button when terms and conditions is automatic
or when it is disabled

* Show message for google pay when gateway responds with a message

Co-authored-by: Alessio Zampatti <alessio.zampatti@adyen.com>
Co-authored-by: Attila Kiss <42297201+cyattilakiss@users.noreply.github.com>

Orders paid by alternative payment methods have the state new after
order creation therefore when an authorization success=false
notification is being processed close orders with state new as well not
just the payment_review state ones

Apply getNotificationsCanCancel() for all cases not just when the order
is in payment_review state