Add new .NET 10 Blazor telemetry features example

[msuddaby]

As per the discussion in #2329, I've added a few example services to leverage the new .NET 10 Blazor Server telemetry features. These examples demonstrate how they can be used with Sentry.

Improvements:

• The Sentry issue feed will display the page name beside the issue ID (instead of GET /_blazor)
• Breadcrumbs will now track UI clicks and navigation
• UI clicks show which method was executed
• Tags now include the Blazor circuit id, the component, and the route

#skip-changelog

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.91%. Comparing base (adc75c0) to head (7b63b2c).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4769      +/-   ##
==========================================
+ Coverage   73.87%   73.91%   +0.04%     
==========================================
  Files         485      485              
  Lines       17689    17686       -3     
  Branches     3497     3494       -3     
==========================================
+ Hits        13067    13072       +5     
+ Misses       3761     3756       -5     
+ Partials      861      858       -3     

☔ 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.

[jamescrosswell]

Thank you @msuddaby - this is a huge improvement over the sample we had so I'm all good with this. About the only thing that we might want to change is removing the registration of the OTEL metrics as I don't think this is required and adds complexity.

At some stage we could potentially look at using some of this work to build an official integration. It looks like a lot of what you've done to get meaningful names etc. for breadcrumbs could be used to create more meaningful and connected traces. Sentry will be changing how tracing works under the hood though, so we'd probably want to complete that work first.

[jamescrosswell]

@msuddaby this is looking great.

There's a problem with our CI servers at the moment, so build / .NET (linux-musl-x64) is failing on all of our branches... you can ignore that.

I also ran dotnet format locally since our CI servers can't do this automatically for forked repos.

Huge thank you for the contribution 🙏🏻 ⭐ 🚀

[Flash0ver]

@msuddaby, thank you very much for the work you put in to making our samples better. Please reach out to me via Email ([email protected]), or on any of my socials (see my GitHub profile @Flash0ver), we may have SWAG for you in store 😉.