feat (cherry-pick): added test network as selected network if globally selected for…

[NidhiKJha]

… connection Request (#27980)

This PR is to select a test network in the default selected networks list if its the globally selected network at the time of connection request.

Related issues

Fixes:
#27891 ## Manual testing steps

1. Run extension with yarn start
2. Switch to Sepolia
3. Go to test-dapp, click on connect.
4. In the connections page, check Sepolia is the selected along with non test networks
5. Click confirm, dapp should be connected to MM and user should be on Sepolia network in MM.

Screenshots/Recordings

Before

Screen.Recording.2024-10-21.at.3.09.20.PM.mov

After

Screen.Recording.2024-10-21.at.3.07.23.PM.mov

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.

Description

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

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.

[metamaskbot]

Builds ready [1eb190f]

• 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, 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 (2023 ± 100 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	328	2388	1776	625	300
		domContentLoaded	1648	2252	1992	183	88
		load	1657	2401	2023	208	100
		domInteractive	16	137	53	27	13
		backgroundConnect	9	149	40	40	19
		firstReactRender	56	298	117	50	24
		getState	5	73	25	23	11
		initialActions	0	0	0	0	0
		loadScripts	1177	1726	1497	163	78
		setupStore	12	118	38	32	15
		uiStartup	1881	3027	2312	302	145

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 3.1 KiB (0.06%)
• ui: 1.28 KiB (0.02%)
• common: 284 Bytes (0.00%)

[metamaskbot]

No release label on PR. Adding release label release-12.6.0 on PR, as PR was cherry-picked in branch 12.6.0.