fix(astro): Fix astro trace propagation issues

[mydea]

Noticed this while working on #14481.

This PR fixes a bug in our opentelemetry code that lead to invalid empty span IDs being generated in certain cases.
Instead, we now generate valid (but random) span IDs in this case.

Additionally, I also noticed that the way we try-catched the astro server request code lead to the http.server span not being attached to servers correctly - we had a try-catch block outside of the startSpan call, where we sent caught errors to sentry. but any error caught this way would not have an active span (because by the time the catch part triggers, startSpan is over), and thus the http.server span would not be attached to the error. By moving this try-catch inside of the startSpan call, we can correctly assign the span to errors. I also tried to add some tests to this - there is still a problem in there which the tests show, which I'll look at afterwards (and/or they may get fixed by #14481)

UPDATE: Turns out part of this, the generation of an '' span ID, has other implications - otel ignores this as it is invalid, so changing this breaks the pure otel E2E apps. I'll tackle this separately, this PR only handles better try-catching of error traces now.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
655	1	654	31

View the top 1 failed tests by shortest run time

errors.server.test.ts server-side errors › captures SSR error

Stack Traces | 0.441s run time

errors.server.test.ts:5:3 captures SSR error

To view more test analytics, go to the Test Analytics Dashboard
📢 Thoughts on this report? Let us know!