temp+feat: cp-13.3.1 bump solana snap to 2.3.10 (#36129)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

This PR bumps the Solana snap to version `2.3.10`.

## **Changelog**

CHANGELOG entry: Added a mechanism on the Solana snap to time out
websocket subscriptions
([#525](MetaMask/snap-solana-wallet#525))
CHANGELOG entry: Offloaded the assets and transactions sync from account
creation on the Solana snap
([#528](MetaMask/snap-solana-wallet#528))
CHANGELOG entry: Enforced proper assets state sync between the Solana
snap and the client
([#529](MetaMask/snap-solana-wallet#529))

## **Related issues**

Fixes:

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] 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](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
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.

Author: runway-github[bot]

.github/CODEOWNERS

@@ -99,21 +99,20 @@ app/scripts/constants/snaps.ts       @MetaMask/core-platform
 # Co-owned by Confirmations and Snaps
 ui/components/app/metamask-template-renderer @MetaMask/confirmations @MetaMask/core-platform
 
-# Core Extension UX
-ui/components/app/whats-new-popup     @MetaMask/core-extension-ux
-ui/css                                @MetaMask/core-extension-ux
-ui/pages/home                         @MetaMask/core-extension-ux
-ui/pages/core                         @MetaMask/core-extension-ux
-ui/components/multichain/             @MetaMask/core-extension-ux
-
-# Co-owned by accounts and core-extension-ux
-ui/components/multichain/multi-srp/              @MetaMask/accounts-engineers @MetaMask/core-extension-ux
-ui/components/multichain/account-picker/         @MetaMask/accounts-engineers @MetaMask/core-extension-ux
-ui/components/multichain/account-details/        @MetaMask/accounts-engineers @MetaMask/core-extension-ux
-ui/components/multichain/account-overview/       @MetaMask/accounts-engineers @MetaMask/core-extension-ux
-ui/components/multichain/account-list-item/      @MetaMask/accounts-engineers @MetaMask/core-extension-ux
-ui/components/multichain/account-list-menu/      @MetaMask/accounts-engineers @MetaMask/core-extension-ux
-ui/components/multichain/account-list-item-menu/ @MetaMask/accounts-engineers @MetaMask/core-extension-ux
+# Wallet UX
+ui/components/app/whats-new-popup     @MetaMask/wallet-ux
+ui/css                                @MetaMask/wallet-ux
+ui/pages/home                         @MetaMask/wallet-ux
+ui/components/multichain/             @MetaMask/wallet-ux
+
+# Co-owned by accounts and wallet-ux
+ui/components/multichain/multi-srp/              @MetaMask/accounts-engineers @MetaMask/wallet-ux
+ui/components/multichain/account-picker/         @MetaMask/accounts-engineers @MetaMask/wallet-ux
+ui/components/multichain/account-details/        @MetaMask/accounts-engineers @MetaMask/wallet-ux
+ui/components/multichain/account-overview/       @MetaMask/accounts-engineers @MetaMask/wallet-ux
+ui/components/multichain/account-list-item/      @MetaMask/accounts-engineers @MetaMask/wallet-ux
+ui/components/multichain/account-list-menu/      @MetaMask/accounts-engineers @MetaMask/wallet-ux
+ui/components/multichain/account-list-item-menu/ @MetaMask/accounts-engineers @MetaMask/wallet-ux
 
 # Web3Auth / Onboarding
 ui/pages/onboarding-flow              @MetaMask/web3auth

.github/actions/page-load-benchmark-comment/action.yml

@@ -2,41 +2,38 @@
 
 To maintain a consistent and efficient development workflow, we have set specific label guidelines for all pull requests (PRs). Please ensure you adhere to the following instructions:
 
-## Mandatory team label (automated)
+### Mandatory team labels:
 
 - **Internal Developers**: Every PR raised by an internal developer must include a label prefixed with `team-` (e.g., `team-extension-ux`, `team-extension-platform`, etc.). This indicates the respective internal team responsible for the PR.
 
 - **External Contributors**: PRs submitted by contributors who are not part of the organization will be automatically labeled with `external-contributor`.
 
-## Mandatory checklog entry or label (manual addition)
+It's essential to ensure that PRs have the appropriate labels before they are considered for merging.
 
-The releases changelog generation is based on PR's changelog entries.
-The check can be bypassed when necessary, either by setting the changelog entry to "null" or by adding following label:
+### Mandatory release version labels:
 
-- **no-changelog**: PR's changes do not need to be included in the changelog.
-
-## Optional labels (manual addition)
-
-Any label can be manually added on demand depending on the PR's content. For instance, the label **QA passed** will indicate that a thorough manual testing has been performed and the PR is ready to be merged. In addition, following labels have some specific use cases.
+- **release-x.y.z**: This label is automatically added to a PR and its linked issues upon the PR's merge. The `x.y.z` in the label represents the version in which the changes from the PR will be included. This label is auto-generated by a [GitHub action](../workflows/add-release-label.yml), which determines the version by incrementing the minor version number from the most recent release. Manual intervention is only required in specific cases. For instance, if a merged PR is cherry-picked into a release branch, typically done to address Release Candidate (RC) bugs, the label would need to be manually updated to reflect the correct version.
+- **regression-prod-x.y.z**: This label is automatically added to a bug report issue at the time of its creation. The `x.y.z` in the label represents the version in which the bug first appeared. This label is auto-generated by a [GitHub action](../workflows/check-template-and-add-labels.yml), which determines the `x.y.z` value based on the version information provided in the bug report issue form. Manual intervention is only necessary under certain circumstances. For example, if a user submits a bug report and specifies the version they are currently using, but the bug was actually introduced in a prior version, the label would need to be manually updated to accurately reflect the version where the bug originated.
+- **regression-RC-x.y.z**: This label is manually added to a bug report issue by release engineers when a bug is found during release regerssion testing phase. The `x.y.z` in the label represents the release candidate (RC) version in which the bug's been discovered.
 
-### Bypass Quality Gates
+### Optional labels:
 
-Using any of these labels should be exceptional in case of CI friction and urgencies. Please use them reasonably and verify new changes and regressions manually.
+- **regression-main**: This label can manually be added to a bug report issue at the time of its creation if the bug is present on the development branch, i.e., `main`, but is not yet released in production.
+- **feature-branch-bug**: This label can manually be added to a bug report issue at the time of its creation if the bug is present on a feature branch, i.e., before merging to `main`.
+- **needs-qa**: If the PR includes a new features, complex testing steps, or large refactors, this label must be added to indicated PR requires a full manual QA prior being merged and added to a release.
 
-- **skip-e2e-quality-gate**: This label will disable the default test retries for E2E test files modified in the PR. Useful when making large refactors or when changes don't pose flakiness risk.
+### Labels prohibited when PR needs to be merged:
 
-### Block merge if any is present
+Any PR that includes one of the following labels can not be merged:
 
 - **needs-qa**: The PR requires a full manual QA prior to being merged and added to a release.
+- **QA'd but questions**: The PR has been checked by QA, but there are pending questions or clarifications needed on minor issues that were found.
+- **issues-found**: The PR has been checked by QA or other reviewers, and appeared to include issues that need to be addressed.
 - **need-ux-ds-review**: The PR requires a review from the User Experience or Design System teams.
 - **blocked**: There are unresolved dependencies or other issues blocking the progress of this PR.
 - **stale**: The PR has not had recent activity in the last 90 days. It will be closed in 7 days.
 - **DO-NOT-MERGE**: The PR should not be merged under any circumstances.
 
-## Release version label (automated)
-
-- **release-x.y.z**: This label is automatically added to a PR and its linked issues upon the PR's merge. The `x.y.z` in the label represents the version in which the changes from the PR will be included. This label is auto-generated by a [GitHub action](../workflows/add-release-label.yml), which determines the version by incrementing the minor version number from the most recent release. Manual intervention is only required in specific cases. For instance, if a merged PR is cherry-picked into a release branch, typically done to address Release Candidate (RC) bugs, the label would need to be manually updated to reflect the correct version.
-
 To maintain code quality and project integrity, it's crucial to respect these label guidelines. Please ensure you review and update labels appropriately throughout the PR lifecycle.
 
 Thank you for your cooperation!

.github/e2e-filter-rules.yml

@@ -42,6 +42,8 @@ async function main(): Promise<void> {
 
   const preventMergeLabels = [
     'needs-qa',
+    "QA'd but questions",
+    'issues-found',
     'need-ux-ds-review',
     'blocked',
     'stale',

.github/guidelines/LABELING_GUIDELINES.md

@@ -140,7 +140,6 @@ async function main(): Promise<void> {
       }
       // Add area-Sentry label to the bug report issue
       await addAreaSentryLabelToIssue(octokit, labelable);
-      await checkAndRemoveNeedsTriageIfFullyLabeled(octokit, labelable);
       process.exit(0); // Stop the process and exit with a success status code
     }
 
@@ -166,22 +165,18 @@ async function main(): Promise<void> {
       if (context.payload.action === 'opened') {
         await addNeedsTriageLabelToIssue(octokit, labelable);
       }
-      await checkAndRemoveNeedsTriageIfFullyLabeled(octokit, labelable);
-
     } else {
       const errorMessage =
         "Issue body does not match any of expected templates ('general-issue.yml' or 'bug-report.yml').\n\nMake sure issue's body includes all section titles.\n\nSections titles are listed here: https://github.com/MetaMask/metamask-extension/blob/main/.github/scripts/shared/template.ts#L14-L37";
       console.log(errorMessage);
 
-      // Add label to indicate issue does not match any template
+      // Add label to indicate issue doesn't match any template
       await addLabelToLabelable(octokit, labelable, invalidIssueTemplateLabel);
-      await checkAndRemoveNeedsTriageIfFullyLabeled(octokit, labelable);
 
       // Github action shall fail in case issue body doesn't match any template
       core.setFailed(errorMessage);
       process.exit(1);
     }
-
   } else if (labelable.type === LabelableType.PullRequest) {
     if (templateType === TemplateType.PullRequest) {
       console.log("PR matches 'pull-request-template.md' template.");
@@ -190,22 +185,6 @@ async function main(): Promise<void> {
         labelable,
         invalidPullRequestTemplateLabel,
       );
-
-      // Skip changelog check if PR has "no-changelog" label
-      const hasNoChangelogLabel = labelable.labels?.some(
-        (label) => label.name === "no-changelog"
-      );
-
-      // Require changelog entry
-      if (hasNoChangelogLabel) {
-        console.log(`PR ${labelable.number} has "no-changelog" label. Skipping changelog entry check.`);
-      } else if (!hasChangelogEntry(labelable.body)) {
-        const errorMessage = `PR is missing a valid "CHANGELOG entry:" line.`;
-        console.log(errorMessage);
-
-        core.setFailed(errorMessage);
-        process.exit(1);
-      }
     } else {
       const errorMessage = `PR body does not match template ('pull-request-template.md').\n\nMake sure PR's body includes all section titles.\n\nSections titles are listed here: https://github.com/MetaMask/metamask-extension/blob/main/.github/scripts/shared/template.ts#L40-L47`;
       console.log(errorMessage);
@@ -405,65 +384,3 @@ async function userBelongsToMetaMaskOrg(
 
   return Boolean(userBelongsToMetaMaskOrgResult?.user?.organization?.id);
 }
-
-// This function checks if the PR description has a changelog entry
-function hasChangelogEntry(body: string): boolean {
-  // Remove HTML comments (including multiline)
-  const uncommentedBody = body.replace(/<!--[\s\S]*?-->/g, "");
-
-  // Split body into lines
-  const lines = uncommentedBody.split(/\r?\n/);
-
-  // Find the line starting with "CHANGELOG entry:"
-  const changelogLine = lines.find(line => line.trim().startsWith("CHANGELOG entry:"));
-
-  if (!changelogLine) {
-    console.log("Changelog entry line missing");
-    return false;
-  }
-
-  // Extract everything after the prefix, tolerating extra spaces after the colon
-  const match = changelogLine.match(/^\s*CHANGELOG entry:\s*(.*)$/);
-  const entry = match?.[1]?.trim() ?? "";
-
-  if (entry === "") {
-    console.log("Changelog entry is empty");
-    return false;
-  }
-
-  console.log(`Changelog entry found: ${entry}`);
-  return true; // allow any non-empty value, including "null"
-}
-
-// This function checks if issue has both team and severity labels and removes needs-triage label if present
-async function checkAndRemoveNeedsTriageIfFullyLabeled(
-  octokit: InstanceType<typeof GitHub>,
-  issue: Labelable,
-): Promise<void> {
-  let hasTeamLabel = false;
-  let hasSeverityLabel = false;
-
-  for (const label of issue.labels || []) {
-    // Check for team labels
-    if (
-      label.name.startsWith('team-') ||
-      label.name === externalContributorLabel.name
-    ) {
-      console.log(`Issue contains a team label: ${label.name}`);
-      hasTeamLabel = true;
-    }
-    // Check for severity labels (Sev0-urgent, Sev1-high, etc.)
-    if (/^Sev\d-\w+$/.test(label.name)) {
-      console.log(`Issue contains a severity label: ${label.name}`);
-      hasSeverityLabel = true;
-    }
-  }
-
-  // If both team and severity labels are present, remove needs-triage label
-  if (hasTeamLabel && hasSeverityLabel) {
-    console.log(
-      'Both team and severity labels found. Removing needs-triage label if present...',
-    );
-    await removeLabelFromLabelableIfPresent(octokit, issue, needsTriageLabel);
-  }
-}

.github/scripts/check-pr-has-required-labels.ts

@@ -103,7 +103,7 @@ async function main(): Promise<void> {
     process.exit(1);
   }
 
-  const issueBody = `**What is this bug report issue for?**\n\n1. This issue is used to track release dates on this [Github Project board](https://github.com/orgs/MetaMask/projects/${projectNumber}/views/${projectViewNumber}), which content then gets pulled into our metrics system.\n\n2. This issue is also used by our Zapier automations, to determine if automated notifications shall be sent on Slack for release \`${releaseVersion}\`. Notifications will only be sent as long as this issue is open.\n\n**Who created and/or closed this issue?**\n\n- This issue was automatically created by a GitHub action upon the creation of the release branch \`release/${releaseVersion}\`, indicating the release was cut.\n\n- This issue gets automatically closed by another GitHub action, once the release branch \`release/${releaseVersion}\` merges into \`stable\`, indicating the release is prepared for store submission.`;
+  const issueBody = `**What is this bug report issue for?**\n\n1. This issue is used to track release dates on this [Github Project board](https://github.com/orgs/MetaMask/projects/${projectNumber}/views/${projectViewNumber}), which content then gets pulled into our metrics system.\n\n2. This issue is also used by our Zapier automations, to determine if automated notifications shall be sent on Slack for release \`${releaseVersion}\`. Notifications will only be sent as long as this issue is open.\n\n**Who created and/or closed this issue?**\n\n- This issue was automatically created by a GitHub action upon the creation of the release branch \`Version-v${releaseVersion}\`, indicating the release was cut.\n\n- This issue gets automatically closed by another GitHub action, once the release branch \`Version-v${releaseVersion}\` or \`release/${releaseVersion}\` merges into \`main\`, indicating the release is prepared for store submission.`;
   const issueId = await createIssue(octokit, repoOwner, planningRepoName, issueTitle, issueBody, [regressionLabelTestingId, typeBugLabelId, teamLabelId]);
 
   // Retrieve project, in order to obtain its ID