feat: Adding more metrics parameters for signature decoding

[jpuri]

Description

Adding more parameters to signature decoding metrics:

1. decoding_latency - this should capture the amount time it takes to display the decoding results to users. This is similar to the existing simulation_latency property for simulations.
2. decoding_description - this should capture any error message sent along by the API. This is similar to how security_alerts_description property works for blockaid.
3. decoding_in_progress - this value should be passed to decoding_response property when the user approves or rejects the signature request before we display the decoding output.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/3778

Manual testing steps

1. Enable metrics locally, go to test dapp
2. Submit permit sign
3. Check metrics for signature

Screenshots/Recordings

NA

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension 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.

[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.

[metamaskbot]

Builds ready [8a3cf34]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1732 ± 45 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1531	1877	1735	96	46
		domContentLoaded	1521	1856	1712	90	43
		load	1530	1866	1732	94	45
		domInteractive	24	103	51	25	12
		backgroundConnect	9	59	23	15	7
		firstReactRender	16	74	44	25	12
		getState	4	67	15	18	8
		initialActions	0	1	0	0	0
		loadScripts	1118	1412	1288	79	38
		setupStore	6	53	10	10	5
		uiStartup	1768	2139	1972	103	50

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 423 Bytes (0.01%)
• common: 0 Bytes (0.00%)