fix: silence PollingBlockTracker Sentry error emit

[frankvonhoven]

Description

1. What is the reason for the change?

• Sentry PollingBlockTracker errors were very noisy (see related issue)

2. What is the improvement/solution?

• Silencing the unhandled error as we weren't able to determine sources of errors
• Patch the web3-provider-engine node module with change
• The PollingBlockTracker will be replaced in the network-controller v9 - which is expected to be released soon

Related issues

Fixes: #7579

Manual testing steps

1. Switch between networks
2. Swap some crypto
3. Send some crypto
4. Shouldn't see any PollingBlockTracker errors like in the related issue in Sentry

Screenshots/Recordings

Switch Networks

switch-network.mp4

Swap

swap.mp4

Send

send.mp4

Transaction History

history.mp4

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f2fd964b-7888-4df9-bd6b-ec9e1ba2d01d
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[Cal-L]

Left a comment

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b9088e7) 35.09% compared to head (52a9410) 35.09%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7733   +/-   ##
=======================================
  Coverage   35.09%   35.09%           
=======================================
  Files        1035     1035           
  Lines       27526    27526           
  Branches     2311     2311           
=======================================
  Hits         9661     9661           
  Misses      17345    17345           
  Partials      520      520           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Cal-L]

Could we also provide evidence showing that these aren't broken since PollingBlockTracker is used by both network controller and transaction controller?

• Switching networks between testnets as well as other chains such as BNB, polygon, etc
• Ensuring that transaction history still appears properly in the activity view
• Perform some transactions on mainnet such as send, swap, etc

[Cal-L]

LGTM

[chrisleewilcox]

@frankvonhoven @Cal-L I moved this back to dev review. E2E failed to build. Can you update branch and rerun E2E for this PR?

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[Cal-L]

Lgtm

[chrisleewilcox]

LGTM