Make Venmo ineligible if shipping callback is present & displayOnly includes "vaultable" 👾

[spencersablan]

Description

• 🚀 Update to eligibility in Venmo config - If a shipping callback is present and displayOnly: ["vaultable"], we should not show the venmo button.
• 🆕 _**New param for the buttons called hasShippingCallback**_ - We weren't passing onShippingAddressChangeoronShippingOptionsChange` to SCNW, but we needed a way to know if a shipping callback existed. Instead of passing these callbacks themselves, I just added this boolean one query param. S/O to @wsbrunson for this idea!
• 📝 Added unit tests for Venmo config - For now, its just covering the logic I added, but figured it might be nice to have.
• 🏈 Pass displayOnly & hasShippingCallback - These params needed to go from the Buttons & Marks component, down to isFundingEligible.
• 🌠 Update Marks component to accept displayOnly - Since we were making these changes to the buttons component, I wanted to make sure the Marks eligibility was aligned as closely as possible.

Why are we making these changes? Include references to any related Jira tasks or GitHub Issues

JIRA: DTPPCPSDK-2321

Reproduction Steps (if applicable)

Setup

• Pull changes to local
• Make sure checkout-components is aliased in CSNW & SCNW.
• In checkout-components - npm run build
• In CSNW & SCNW - npm run debug
• Make sure Venmo is enabled on your local test page.

Testing

• On your test page, try adding a shipping callback and displayOnly: ["vaultable"] to your buttons component. You should not see the Venmo button
• Try removing one or the other params and the Venmo button should show up again.

❤️ Thank you!

[nikrom17]

Looks good to me 🚀