feat: allow a custom provider to be passed to Connect methods

[janniks]

This PR was published to npm with the alpha versions:

• connect npm install @stacks/connect@7.3.2-alpha.111be12.0 --save-exact
• connect-react npm install @stacks/connect-react@22.1.2-alpha.111be12.0 --save-exact
• connect-ui npm install @stacks/connect-ui@6.1.2-alpha.111be12.0 --save-exact

Description

Allow a custom StacksProvider object to be passed into most Connect methods.

• Attempt at making this issue better: Resolve StacksProvider conflict across wallets #325

• Should the provider be a part of the options, or does this separate second param make more sense?

Example

import { authenticate } from '@stacks/connect';

// This will open only the Hiro Wallet
authenticate({ ...normalAuthOptions }, HiroWalletProvider); // <---

Type of Change

• New feature
• Bug fix
• API reference/documentation update
• Other

[changeset-bot]

⚠️ No Changeset found

Latest commit: 111be12

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
connect-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 25, 2023 7:07pm

[kyranjamie]

Nice work @janniks