chore(sc-65330): Improve error reporting for apps by reporting to Sentry

[HappyPaul55]

This PR improves error reporting for apps by integrating Sentry. It includes the necessary configurations and updates to the main.tsx file to handle errors effectively.

[Copilot]

Pull Request Overview

This PR integrates Sentry for enhanced error reporting by adding build-time plugins, runtime initialization, and CI configuration updates.

• Adds the Sentry Vite plugin and sourcemap support in vite.config.ts
• Initializes Sentry at runtime via a new instrument.ts script and imports it in main.tsx
• Updates CI workflow to inject Sentry secrets and disable reporting on non-tag builds
• Adds Sentry packages and removes the react-error-boundary dependency

Reviewed Changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
vite.config.ts	Configure sentryVitePlugin conditionally and enable sourcemaps
src/main.tsx	Import Sentry and the instrumentation script
src/instrument.ts	Initialize Sentry based on URL parameters
package.json	Add @sentry/react and @sentry/vite-plugin; remove error boundary dep
.github/workflows/subworkflow-build.yml	Pass Sentry env vars to CI and adjust build logic

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (2)

package.json:28

• The react-error-boundary dependency was removed but no replacement boundary is implemented; verify that any existing error boundary logic is replaced to prevent runtime issues.

"react-error-boundary": "^4.1.2",

src/main.tsx:1

• [nitpick] Consider wrapping the <App /> component in a Sentry.ErrorBoundary or providing a custom fallback UI to ensure UI errors are properly captured and communicated.

import * as Sentry from '@sentry/react';

[github-actions]

Build for commit 8cc4629 deployed to: https://mondaycom-pr-41.ci.next.deskprodemo.com

URLs:
https://mondaycom-pr-41.ci.next.deskprodemo.com/horizon-ui/app