feat: autoconnect global loading

[tmm]

Inspo #37 h/t @sammdec

When Provider autoConnect={true}, useConnect hook has loading set to true on load. After the auto connect process is tried, the global connecting value is switch back to false. (Maybe useful in the future to also set the global connector so you know what connector is attempting to auto connect.)

Decided to not make changes to useAccount loading because it isn't involved at this step of the "connection" process.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 701108b

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]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/zoo/wagmi/C6aUXuSqziCMGFVqmt8anF4pEq9Z
✅ Preview: https://wagmi-git-tmm-autoconnect-flag-zoo.vercel.app