feat(remix): add connection check to example page

[shellmayr]

• Uses the new diagnoseSdkConnectivity() function to check whether something is preventing data from reaching sentry feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues sentry-javascript#15821
• If the connection is disturbed, call this out to the user using a banner and link to the docs explaining how to solve the issue
• Contributes to TET-59

Before:

After:

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 6975c2a

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 24.28%. Comparing base (04f3500) to head (6975c2a).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #967   +/-   ##
=======================================
  Coverage   24.28%   24.28%           
=======================================
  Files         121      121           
  Lines       12883    12883           
  Branches      715      715           
=======================================
  Hits         3128     3128           
  Misses       9734     9734           
  Partials       21       21           

Flag	Coverage Δ
unit-tests	24.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Lms24]

l: let's avoid potential eslint warnings about empty useEffect arrays

Suggested change

	}, []);
	}, [setIsConnected]);

[s1gr1d]

Btw some context here (we discussed this offline already, but just if someone is interested): The set... functions have a stable reference so they won't cause useEffect to fire again. However, it's advised to always include all potential variables to the dependency array.

React docs about set... and stable identities: https://react.dev/reference/react/useState#setstate-caveats