fix: Ensure provider is initialized on reconnect regardless of social_login

[developerfred]

Description

Previously, provider initialization and the auth connect flow were gated by isAuthSupported (tied to the social_login feature). When social_login was disabled this prevented provider.init() from running on startup for already-connected wallets, leaving local account state (e.g. allAccounts / activeCaipAddress) empty until a modal triggered initialization.

This PR:

Always calls provider.init() when the namespace should be synchronized and the connection is active, enclosed in a try/catch to avoid blocking startup on provider errors.
Preserves the existing auth connectExternal flow when isAuthSupported is true.
For non-auth-supported reconnects, explicitly marks the namespace as connected and emits CONNECT_SUCCESS (method: 'wallet') so local account state is populated and existing integrations continue to work.
No changes are made to the social login flows themselves; this is a behavioral fix to ensure consistent account state during initialization.

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-4120
For GH issues: closes #5256

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
• I have tested my changes on the preview link
• Approver of this PR confirms that the changes are tested on the preview link

[vercel]

@developerfred is attempting to deploy a commit to the Reown Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 43329cf

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

[github-actions]

All contributors have signed the CTA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[developerfred]

I have read the CTA Document and I hereby sign the CTA