timeseries [6/6] RUM-13949 Add end-to-end timeseries verification tests with CSV fixtures

[satween]

What does this PR do?

Adds a self-contained end-to-end test suite for the timeseries pipeline using CSV-driven input fixtures and golden JSON files, without any real Android API dependencies. Includes CSVReader, CsvTimeseries (a synchronous, executor-free test double mirroring RumSessionScopeTimeseriesFactory), TimeseriesEndToEndTest, and the accompanying CSV input and expected JSON fixture files.

Motivation

Provides regression coverage that the full memory and CPU batch outputs match the expected wire format exactly, catching any serialization regressions independently of mock-heavy unit tests.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Make sure you discussed the feature or bugfix with the maintaining team in an Issue
• Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

[satween]

• timeseries [6/6] RUM-13949 Add end-to-end timeseries verification tests with CSV fixtures #3436 👈 (View in Graphite)
• timeseries [5/6] RUM-13949 Wire timeseries collection into RUM session lifecycle #3435
• timeseries [4/6] RUM-13949 Add memory timeseries serializer and session factory #3434
• timeseries [3/6] RUM-13949: Add CPU timeseries data-point reader and serializer #3433
• timeseries [2/6] RUM-13949: Implement timeseries pipeline infrastructure #3432
• timeseries RUM-13949: Add timeseries JSON schemas and regenerate API surface #3431
• feature/timeseries

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (tvaleev/feature/RUM-13949/timeseries-rum-session-wiring@af31b3d). Learn more about missing BASE report.

Additional details and impacted files

@@                                    Coverage Diff                                     @@
##             tvaleev/feature/RUM-13949/timeseries-rum-session-wiring    #3436   +/-   ##
==========================================================================================
  Coverage                                                           ?   72.34%           
==========================================================================================
  Files                                                              ?      977           
  Lines                                                              ?    35895           
  Branches                                                           ?     5983           
==========================================================================================
  Hits                                                               ?    25968           
  Misses                                                             ?     8296           
  Partials                                                           ?     1631           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6e1f3b8a34

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Enforce primitive types in golden JSON comparison

When a serializer accidentally changes a numeric field in the wire payload to a JSON string with the same characters, this comparison still passes because the expected.isString || actual.isString branch compares only asString values. That defeats the purpose of these golden fixtures as exact wire-format checks; for example, an actual "1700000001000000000" would be accepted for an expected numeric 1700000001000000000. Please require both primitives to have the same JSON type before comparing their values.

Useful? React with 👍 / 👎.

The base branch was changed.