ref(solid): Add mechanism to error captured by withSentryErrorBoundary

[Lms24]

Adds a mechanism following the trace origin naming conventions. Decided to go with handled: true since AFAICT, users always have to provide a fallback (as opposed to react ErrorBoundary where this is optional)

closes #17264

[andreiborza]

Thanks!

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
⚠️ Warning: Base artifact is not the latest one, because the latest workflow run is not done yet. This may lead to incorrect results. Try to re-run all tests to get up to date results.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,157	-	8,921	+3%
GET With Sentry	1,198	13%	1,256	-5%
GET With Sentry (error only)	5,904	64%	6,142	-4%
POST Baseline	1,175	-	1,198	-2%
POST With Sentry	456	39%	503	-9%
POST With Sentry (error only)	1,015	86%	1,068	-5%
MYSQL Baseline	3,288	-	3,324	-1%
MYSQL With Sentry	382	12%	463	-17%
MYSQL With Sentry (error only)	2,593	79%	2,726	-5%

View base workflow run