refactor: use chain id for the transports array mapping

[enesozturk]

Description

We previously refactored our logic to create transports array for wagmi, to use chain object directly instead of chain.id in the defaultWagmiReactConfig.ts. But we still use chain.id in the defaultWagmiCoreConfig.ts. Wagmi is looking for chainID while mapping the transport objects, as could be seen in any dApp that uses our package >=5.0.6:

TypeError: rest.transports[chainId] is not a function
    at Object.transport (createConfig.js:121:66)
    at createClient (createClient.js:15:51)
    at Object.getClient (createConfig.js:115:72)

This PR introduces changes to revert this back.

Type of change

• Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Associated Issues

For Linear issues: Closes APKT-xxx
For GH issues: closes #...

Showcase (Optional)

If there is a UI change include the screenshots with before and after state.
If new feature is being introduced, include the link to demo recording.

Checklist

• Code in this PR is covered by automated tests (Unit tests, E2E tests)
• My changes generate no new warnings
• I have reviewed my own code
• I have filled out all required sections

[vercel]

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

Name	Status	Preview	Updated (UTC)
web3modal-gallery	✅ Ready (Inspect)	Visit Preview	Jul 30, 2024 2:25pm
web3modal-laboratory	✅ Ready (Inspect)	Visit Preview	Jul 30, 2024 2:25pm

[chris13524]

Sounds like a bug fix, looks good to me!