chore: update CODEOWNERS for bridge related code

[infiniteflower]

Description

This PR updates CODEOWNERS for all Bridge related code.

Related issues

n/a

Manual testing steps

n/a

Screenshots/Recordings

n/a

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.

[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 [4f2bbcd]

• 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, 13, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1911 ± 73 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	262	2280	1829	390	187
		domContentLoaded	1669	2266	1890	154	74
		load	1726	2282	1911	152	73
		domInteractive	27	84	41	19	9
		backgroundConnect	6	59	25	15	7
		firstReactRender	15	84	22	15	7
		getState	84	312	134	44	21
		initialActions	0	0	0	0	0
		loadScripts	1264	1815	1461	147	70
		setupStore	7	12	9	2	1
		uiStartup	1941	2654	2198	202	97

Bundle size diffs

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

[metamaskbot]

Builds ready [7aca15d]

• 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, 13, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1708 ± 55 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1557	2065	1708	121	58
		domContentLoaded	1550	2039	1692	117	56
		load	1557	2045	1708	114	55
		domInteractive	23	42	28	6	3
		backgroundConnect	8	52	16	11	5
		firstReactRender	14	90	24	22	11
		getState	80	377	138	67	32
		initialActions	0	1	0	0	0
		loadScripts	1182	1655	1308	111	53
		setupStore	6	10	7	1	1
		uiStartup	1760	2594	1986	198	95

Bundle size diffs

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

[jclancy93]

I see we have types, like bridge-status.ts that lives outside of this structure. For files like these, should we:

• colocate them in this or a follow on PR?
• Add specific entries for those files here?

Not blocking, just wanted to call out

[infiniteflower]

We can make a new PR to add additional files

[desi]

LGTM