feat: Modify Alchemy provider's api key to be mapped by chain.

[siosio34]

Description

hello. I am using alchemyProvider, but inside alchemy, it is recommended to use different API Keys for each chain, so I changed the internal source.

The documentation code has not been included yet, but if the reflection of the code is judged to be okay, we will also modify the docs.

If you want to support the type of the previous version of the syntax, you can do additional work, but after contacting Alchemy, it seems that it is not encouraged. Same.

Finally, thank you for making a good open source. Thanks to you, my working hours are shorter.

Additional Information

• [O] I read the contributing docs (if this is your first contribution)

Your ENS/address:

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0258af7

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]

@siosio34 is attempting to deploy a commit to the wagmi Team on Vercel.

A member of the Team first needs to authorize it.

[tmm]

Appreciate the PR! The concept of providers per service like this will be removed in v2. It's more trouble than it's worth to hardcode RPC base URLs internally and much better folks specify full RPC URLs. In the meantime, you can use the jsonRpc provider. existing pattern comes from when wagmi used ethers internally.

[siosio34]

@tmm Thank you for your review. ~