fix: 2 Duplicated Signature requests events are triggered for any signature

[segun]

Description

For some reason, this merge is showing this warning on Github

So I cherry picked it to develop and created this new PR.

This is basically a copy and paste of #21791 but this time using develop as base.

Below is the original Description copied over from 21791 for completion

When you click on a signature request that is flagged by PPOM, 2 events are sent to metrics instead of 1.

Expected behavior

Just 1 Signature request should be triggered for a Signature event flagged by PPOM

Related issues

Fixes: #21770

Manual testing steps

1. Launch MM
2. Open background console and open the network app, make sure it's recording network requests
3. Open testdapp
4. Click on any of the signature requests for PPOM e.g Malicious Trade Order
5. Go to background console network tab and see 2 signature requests called as shown in the video
6. Checkout this branch, build and run MM
7. Repeat steps 2-4
8. On the background console, you should now see only 1 signature request sent.

Screenshots/Recordings

Before

2-signature-requests.mp4

After

Screen.Recording.2023-11-10.at.10.39.43.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.

[metamaskbot]

Builds ready [a3c4c1f]

• 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
  • common: 0, 1, 2, 3, 4, 5, 6
  • content-script: 0
  • contentscript: contentscript
  • disable-console: disable-console
  • inpage: inpage
  • policy-load: policy-load
  • sentry-install: sentry-install
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (494 ± 258 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	86	190	111	24	12
		domContentLoaded	69	152	101	21	10
		load	82	1378	494	538	258
		domInteractive	69	152	101	21	10

Bundle size diffs

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