Deprecate Remaining `Span` class and interface fields

[Lms24]

I realized we still have a lot of fields on the Span class and interface that need to be deprecated.

### `Span` Interface
- [x] https://github.com/getsentry/sentry-javascript/pull/10192
- [ ] https://github.com/getsentry/sentry-javascript/pull/10208
- [ ] https://github.com/getsentry/sentry-javascript/pull/10213
- [ ] https://github.com/getsentry/sentry-javascript/pull/10244
- [ ] https://github.com/getsentry/sentry-javascript/pull/10217
- [ ] https://github.com/getsentry/sentry-javascript/pull/10260
- [ ] https://github.com/getsentry/sentry-javascript/pull/10268

### Additional public `Span` class fields
- [ ] https://github.com/getsentry/sentry-javascript/pull/10187
- [x] `Span.endTimestamp` - same as Span.startTimestamp (via #10192)
- [ ] https://github.com/getsentry/sentry-javascript/pull/10197
- [ ] https://github.com/getsentry/sentry-javascript/pull/10199
- [ ] https://github.com/getsentry/sentry-javascript/pull/10189

ref #10033

### Related fields on other interfaces
- [x] https://github.com/getsentry/sentry-javascript/pull/10274
- [ ] https://github.com/getsentry/sentry-javascript/pull/10361

[lforst]

• setHttpStatus should probably stay? It's pretty useful and doesn't hurt, unless I am missing something. can probably just go.
• We have multiple instances where we (and our customers) set start- and endTimestamps. A getter like spanToJson doesn't help here as a migration path. @mydea Can you set the start and end timestamps on otel spans retroactively?
• spanRecorder can likely be deprecated and be an implementation detail on the span object/class itself.

The rest looks good to me 👍

[Lms24]

We have multiple instances where we (and our customers) set start- and endTimestamps. A getter like spanToJson doesn't help here as a migration path. @mydea Can you set the start and end timestamps on otel spans retroactively?

setting them via startSpan et al. should still work I think 🤔 ending would need to happen via span.end(endTimestamp)

IdleTransaction (soon to be IdleSpan) in browser adjusts the endTimestamp. I wonder if for this it's enough to make the timestamps of Span protected (so still remove them publicly).

[mydea]

yeah, retroactive update of start/end time is not possible. This needs to be rewritten to buffer the endtime somewhere (?) and set it - but I think I did this here already kind of #9972, so should work, I hope..!

[mydea]

I will deprecate the timestamps!