Slight inconvenience with the WalletConnect sendTransaction process.

### What is this about?

Hello. I'm using MetaMask through the WalletConnect connector and wagmi on mobile. There is a slight inconvenience with the sendTransaction process.

When requesting a signature from MetaMask using the wagmi `sendTransaction` action, if the requested chain differs from the current chain in MetaMask, a network switch flow is triggered.

During this process, when the user confirms the network switch in the MetaMask app, it redirects back to the dapp. However, at the same time, the signature prompt is displayed in the MetaMask app, requiring the dapp user to manually switch back from dapp to the MetaMask app. This causes unnecessary redirection. Therefore, for the sendTransaction request through WalletConnect, I suggest that there should be no redirection after switching the network.

Thanks.

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start by reproducing the wagmi sendTransaction flow through the WalletConnect connector on mobile when the requested chain differs from MetaMask's current chain. Trace the network-switch return behavior between the dapp and MetaMask; done means the switch does not redirect back to the dapp before the signature prompt is completed.

Written by the indexing model from the issue text.