chore/feat: bump SDK to 1.23.0 + port public-safe demo features

[matthew1809]

Summary

• Bump all @dynamic-labs-sdk/* to exact 1.23.0 (public npm lockfile)
• Add business accounts route
• Add MoonPay onramp
• Add EIP-7702 delegation / sponsored EVM transactions
• Add Google Drive backup readiness
• Register the Stellar extension

Test plan

• npm ci / npm run build succeed
• Smoke: auth, wallets, funding (incl. MoonPay), business accounts, gasless dialog, Drive backup

[devin-ai-integration]

Original prompt from mfoyle

Check the JS SDK, and ensure the documentation, and the demo apps are up to date according to the latest release.

If anything is out of sync, check if there aren't existing PRs to update and if so, just ensure they have the changes needed and move on.

Provide only very brief, to the point responses.

If there are no PRs to bring docs up to date, create PRs to update them.
If there are no new PRs to be made, just say that and finish.

Interact only with the following repositories:

JS SDK:

• https://github.com/dynamic-labs/dynamic-js-sdk

Documentation:

• https://github.com/dynamic-labs/documentation

Demo apps:

• https://github.com/dynamic-labs-oss/react-via-js-example-app

• https://github.com/dynamic-labs-oss/vue-via-js-example-app

You only need to look in the following repos: dynamic-labs-oss/react-via-js-example-app, dynamic-labs/documentation, dynamic-labs/dynamic-js-sdk, dynamic-labs-oss/vue-via-js-example-app

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[semgrep-code-dynamic-labs-oss]

Semgrep found 334 block-public-registry-refs-in-package-lock findings:

• package-lock.json
  • L78 - Triage
  • L92 - Triage
  • L502 - Triage
  • L553 - Triage
  • L583 - Triage
  • L593 - Triage
  • L623 - Triage
  • L628 - Triage
  • L644 - Triage
  • L685 - Triage
  • 324 more - Triage

package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/which-typed-array/-/which-typed-array-1.1.22.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.

[semgrep-code-dynamic-labs-oss]

Semgrep found 47 block-public-registry-refs-in-package-lock findings:

• package-lock.json
  • L624 - Triage
  • L629 - Triage
  • L645 - Triage
  • L686 - Triage
  • L705 - Triage
  • L715 - Triage
  • L728 - Triage
  • L752 - Triage
  • L765 - Triage
  • L777 - Triage
  • 37 more - Triage

package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/urijs/-/urijs-1.19.11.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.