Resolve "Spike: Investigate value of Sentry vs performance implications"

What does this MR do?

This MR is best reviewed by going through the commits.

• Temporarily stop including the Sentry webpack bundle
  • This will help us measure general performance with one less JS include
• Remove Sentry webpack bundle from webpack configuration
  • Lighten the development and asset load while we conduct the investigation
• Remove Sentry node dependency
  • Lighten the development and asset load while we conduct the investigation
• Wrap and stub Sentry for performance investigation
  • To prevent current usage of Sentry from erroring out
• Update references to @sentry/browser to point at wrapper
  • To prevent current usage of Sentry from erroring out

Screenshots

N/A

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #251179