SqliteSpanExporter drops a span's status and events, so an exception that ended a run is lost (2.11.0)

Finding: In an external report against google-adk 2.11.0 (opentelemetry-sdk 1.42.1, Python 3.11.13, Linux), SqliteSpanExporter reportedly does not persist span status or events, so a span ended by an exception reads back with status UNSET and an empty event list (https://github.com/google/adk-python/issues/7484). Reported details: The reporter says OpenTelemetry records an exception both as ERROR status with a description and as an exception event carrying type, message and stack trace, and that ADK's trace_tool_call and node_tracing do the same. According to the report, the spans table has columns for ids, parent, name, start/end times, session_id, invocation_id and attributes_json only, and _row_to_readable_span rebuilds spans without status or events. The reported output was status read back: UNSET and events read back: []. The reporter says the table on main is identical, and that the problem occurs every time. Reproduction as described: The report includes a short script that needs no key or network. It creates a SqliteSpanExporter on a temporary database, wraps it in a SimpleSpanProcessor, raises a ValueError inside start_as_current_span, and then calls get_all_spans_for_session. The expected result per the reporter is status ERROR with a description and an exception event. Diagnosis status: The cause described, missing columns and no restoration of status or events on read, is the reporter's own reading of the code and is not maintainer-confirmed. Practical implication if the report is accurate: exception details for failed runs would not be recoverable from the local SQLite trace store in this version, so errors would need to come from other logs or exporters. Fix status: No pull request, fix commit or release appears in the supplied content. The reporter proposes adding status_code, status_description and events_json columns, using ALTER TABLE ... ADD COLUMN for existing database files, writing them in export, and restoring them on read. That is an unreviewed proposal, not a confirmed fix. Limitations: This is a single external report; it was not reproduced by KFA. There is no maintainer response in the supplied material, and comment coverage may omit middle comments. No workaround is stated.