refactor: rename Provider method switchUrl to connect

[Torres-ssf]

This PR:

• renames the Provider method switchUrl to connect.
• ensures new chain and node data is always fetched when instantiating a new Provider or when updating the Provider url ( connect

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	84.93% (+0.09% 🔼)	5172/6090
🟡	Branches	66.4% (+0.12% 🔼)	759/1143
🟡	Functions	75.09%	850/1132
🟢	Lines	84.81% (+0.1% 🔼)	4953/5840

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / operations.ts	82.42% (-1.1% 🔻)	100%	46.67% (-3.33% 🔻)	82.42% (-1.1% 🔻)

Test suite run success

1237 tests passing in 213 suites.

Report generated by 🧪jest coverage report action from 4cae557

[arboleya]

@LuizAsFight @luizstacio FWIW, I was the one who suggested renaming the connect method to switchUrl during my reviews with @Dhaiwat10 — blame should be given where the blame is due. ✋

The reasoning against the connect terminology is that the provider doesn't seem to connect to anything, so much so that we have no disconnect method. Unlike a Database/Socket connection that manages connection pools, TTL, handshakes, etc., it only serves as a bridge/proxy for fetching remote data. This is my understanding, and if we draw inspiration from standard Wallet dropdowns, an improved choice could be selectNetwork(url: string).

I have zero attachment to this, so feel free to do as you please.

[arboleya]

Approving this as-is, because I know it's been an external request.

However, I left my reasoning behind some points that [I believe] could be improved.

[nedsalk]

Requested changes based on this discussion. Other than that, LGTM.

[camsjams]

I didn't know it changed, no opinion on the name itself. But yea it might have broken developer code.

LGTM