feat: add web integration test setup

[venilinvasilev]

Description:
WIP

[lfdt-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[codecov]

Codecov Report

❌ Patch coverage is 13.29787% with 163 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/LocalProviderWeb.js	0.00%	146 Missing ⚠️
src/client/WebClient.js	34.78%	15 Missing ⚠️
src/browser.js	0.00%	1 Missing ⚠️
src/constants/ClientConstants.js	93.33%	1 Missing ⚠️

Files with missing lines	Coverage Δ
src/client/NodeClient.js	91.43% <100.00%> (-0.13%)	⬇️
src/browser.js	0.00% <0.00%> (ø)
src/constants/ClientConstants.js	94.11% <93.33%> (-0.06%)	⬇️
src/client/WebClient.js	43.50% <34.78%> (-0.55%)	⬇️
src/LocalProviderWeb.js	0.00% <0.00%> (ø)

... and 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ivaylonikolov7]

Great work so far. I’d like to propose adding two distinct React environments to test whether all transactions run successfully in both setups. This is important because the majority of our web clients use React with the SDK.

The two environments should differ in their module bundlers—one using Webpack and the other using Vite. We’ve encountered compatibility issues in the past with different bundlers, so this approach will help us proactively address potential problems.

This setup would also allow us to:

• Integrate WalletConnect with the SDK and verify proper behavior.

• Test functions like executeWithSigner and getReceiptWithSigner, aligning closely with real-world use cases our SDK users encounter.

• Mitigate future problems when we return tree-shaking to the SDK.

I understand this would require considerable effort, might involve adding new development dependencies to the SDK, changes in the tests and some rework on the tests. However, the long-term benefit of reducing recurring compatibility issues makes this a worthwhile investment.

The current implementation is solid; however, I’d like to align it as closely as possible with the real-world use cases our users encounter.