Cherry-pick of #26192 for v12.1.0. Original description:

Description

Fix the automatic tracking of Sentry sessions, and refactor Sentry setup to simplify logic and improve logging.

Specifically:

• Remove all dynamic autoSessionTracking enablement.
• Add a custom Sentry transport to prevent any requests reaching Sentry if metrics are disabled.
• Only consider metrics enabled when preference is set and onboarding is complete.
• Enable Sentry if METAMASK_ENVIRONMENT is not production and SENTRY_DSN_DEV is specified.
• Remove the arguments to the setupSentry function.
  • Since the file already references process.env and global.stateHooks internally.
• Flatten all the functions within setupSentry.js.
  • Since they no longer require a dynamic getState callback.
• Log all Sentry messages via the debug package based on the DEBUG environment variable.
  • Create separate loggers for UI and background to differentiate logs.
  • e.g. DEBUG=metamask:sentry:* in .metamask.rc
• Add additional log messages for easier debug.
  • Including all sent events and completed sessions if METAMASK_DEBUG is enabled.
• Add mock SENTRY_DSN_DEV to Flask and MMI test builds.
• Remove duplication in package scripts.

Related issues

Fixes: #2555 #15691

Manual testing steps

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.