Ensure justification is sanitised

[MoMannn]

Description

1. Reason for change

Presently any string data provided via justification is rendered verbatim to the confirmation screen, which is a vector for UI redressing

Ensure that justification is sufficiently sanitised before rendering (ideally as early as possible).

The following should be enforced, removed, or sanitized: (plus any other necessary validation or sanitisation)

Maximum length
Control characters
JSON or XML
Excessive whitespace
single or double quotes
In case of null/empty justification use default text: No justification was provided for the permission

2. Solution

With Zod we do strict sanitation of Justification hitting all the UI redressing vectors, scripts, zero-width characters, dangerous protocols are mod.

Manual testing steps

1. Open the demo dapp at localhost:8000
2. In Justification box input text you desire to test.
3. Click grant permission.

Screenshots/Recordings

Pre-merge author checklist

• I've followed MetaMask 7715 Permissions Snaps Contributor Docs and MetaMask 7715 Permissions Snaps 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

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.

[jeffsmale90]

A couple of nits, plus the shasum mismatch, but this looks great!

[jeffsmale90]

It's beautiful!

Can you please look into those Cursor flagged issues above, and resolve the shasum mismatch (my least favourite thing).

[jeffsmale90]

LGTM - I am unable to test with null justification, as this needs to be integrated into the SDK.