[FEATURE] #3102 Create a new Target for EditModal and Summary

[larsroettig]

Description

This Pull request allows used to move Braintree in a separated extension also allows third party developers
to create fully integrated payment methods

Breaking Changes in This PR

• PaymentInformation/summary.js renders a "summary" view of a payment method, if configured via intercept, or just a title.
• PaymentInformation/useSummary.js incoming props only expect classes and operations, return props now only isLoading and selectedPaymentMethod.
• PaymentInformation/summary.gql.js export modified to single object instead of queries/mutations properties.
• PaymentInformation/useEditModal.js handleDropinReady renamed to handlePaymentReady
• PaymentInformation/editModal.js no longer uses classes, now renders an "editable" view of a payment method, if configured via intercept.

Related Issue

Closes #3102

Acceptance

Verification Stakeholders

@sirugh

Specification

Verification Steps

1. Add Products to Cart
2. Go to checkout
3. Braintree behave live development branch on edit and summery page
4. There two new extension points

Screenshots / Screen Captures (if appropriate)

Checklist

• I have added tests to cover my changes, if necessary.
• I have added translations for new strings, if necessary.
• I have updated the documentation accordingly, if necessary.

[PWAStudioBot]

	Messages
📖	DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next nightly build run (assuming they are fixed).
📖	Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.

Generated by 🚫 dangerJS against 0899e5e

[sirugh]

Feedback left! Please make sure the propTypes are all correct :)

[larsroettig]

@anthoula I did some tree analyses today, change some imports to lazy and try analyses if we have any rendering problem
but looks like there is not so much to optimize with much more afford

[anthoula]

@anthoula I did some tree analyses today, change some imports to lazy and try analyses if we have any rendering problem
but looks like there is not so much to optimize with much more afford

@larsroettig Thank you for looking into this. Your new changes improved the warning - went from 2.9s to 2.5s. We will open up a follow-up ticket to address the warning, and not hold up this PR.

[sirugh]

Cool, lazy is so easy :)

[anthoula]

✅ QA approved