fix: handle blockaid initialisation failure on settings page

[jpuri]

Description

If PPOM initialisation fails prompt user to try again.

Related issues

Fixes: #8068

Manual testing steps

1. Disconnect device from internet
2. Enable blockaid in settings -> experimental
3. It should show message that initialisation failed

Screenshots/Recordings

Screen.Recording.2023-12-18.at.8.47.24.PM.mov

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/941a6ae3-a8bd-4a22-b637-570871c6926c
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/ppom-validator	0.15.0...0.16.0	None	+9/-0	943 kB	metamaskbot

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: @metamask/eth-query@4.0.0, eth-block-tracker@8.1.0, @metamask/eth-json-rpc-middleware@12.0.1

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

[jpuri]

@SocketSecurity ignore @metamask/eth-json-rpc-middleware@12.0.1
@SocketSecurity ignore @metamask/eth-query@4.0.0
@SocketSecurity ignore eth-block-tracker@8.1.0
@SocketSecurity ignore @metamask/ppom-validator@0.16.0

[segun]

PR looks good, just to fix CI failures.

[blackdevelopa]

looks good to me

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
64.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[jpuri]

https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/09e40d91-c60b-4fab-9af0-7f17b504d5bd