fix: cp-7.58.0 Make burn and null address sending a blocking alert

[OGPoyraz]

Description

This PR aims to make burn/null address sending alert to be a blocking alert.

See the task details for further information

Changelog

CHANGELOG entry: Make burn and null address sending a blocking alert

Related issues

Fixes: #22046

Manual testing steps

N/A

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• 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.

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.

---

Note

Make burn/null address alerts blocking and update tests accordingly.

• Alerts:
  • useBurnAddressAlert: Set isBlocking: true for BurnAddress alert in Severity.Danger.
• Tests:
  • Update useBurnAddressAlert.test.ts to expect isBlocking: true for burn/null address cases (direct and nested recipients, mixed/uppercase casing).

^{Written by Cursor Bugbot for commit 9093654. This will update automatically on new commits. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud