feat: use camelCase for PayPalScriptProvider options

[gregjopa]

This PR upgrades to @paypal/paypal-js@6 for the latest script loading behavior and TypeScript types. This latest release includes support for camelCase options. I've upgrade react-paypal-js to use camelCase for the <PayPalScriptProvider> options prop which should feel more common for JS devs.

This is a breaking change and will be included in the next major version bump of react-paypal-js.

Before

<PayPalScriptProvider options={{ "client-id": "test" }}>

After

<PayPalScriptProvider options={{ clientId: "test" }}>

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (d77028c) 99.71% compared to head (7972062) 99.71%.

❗ Current head 7972062 differs from pull request most recent head cb7a3ca. Consider uploading reports for the commit cb7a3ca to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #360   +/-   ##
=======================================
  Coverage   99.71%   99.71%           
=======================================
  Files          18       18           
  Lines         356      356           
  Branches      111      111           
=======================================
  Hits          355      355           
  Misses          1        1           

Impacted Files	Coverage Δ
src/components/PayPalButtons.tsx	98.36% <ø> (ø)
src/constants.ts	100.00% <ø> (ø)
src/components/PayPalScriptProvider.tsx	100.00% <100.00%> (ø)
src/context/scriptProviderContext.ts	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[dtjones404]

LGTM 🥳! Just wanted to verify if EMPTY_BRAINTREE_AUTHORIZATION_ERROR_MESSAGE should be moved to camelCase as well?

react-paypal-js/src/constants.ts

Line 17 in d77028c

export const EMPTY_BRAINTREE_AUTHORIZATION_ERROR_MESSAGE =

[gregjopa]

LGTM 🥳! Just wanted to verify if EMPTY_BRAINTREE_AUTHORIZATION_ERROR_MESSAGE should be moved to camelCase as well?

Great point @dtjones404! I'll push a commit to fix that.