test: reduce JSON multi-batch coverage

[vyasr]

Description

Keep the representative small and large JSON multi-batch chunk sizes while removing redundant middle sizes. The remaining cases still exercise many batches and a range exceeding one batch.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7bc324d7-c5b9-4323-8c81-4a848fb04d1f

📥 Commits

Reviewing files that changed from the base of the PR and between 89dac81 and 3d61bed.

📒 Files selected for processing (1)

• cpp/tests/large_strings/json_tests.cpp

Included review availability: Your plan provides up to 12 included reviews per hour; 4 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• Tests

  • Updated large-string JSON test coverage for multi-batch ranges.
  • Tests now focus on small ranges and oversized ranges; intermediate half-batch and single-batch scenarios are no longer covered.

• Documentation

  • Updated copyright year information in the test documentation.

Walkthrough

The JSON large-string test updates the copyright notice and revises MultiBatch coverage to document and test small multi-batch and oversized ranges.

Changes

JSON large-string test

Layer / File(s)	Summary
MultiBatch range coverage cpp/tests/large_strings/json_tests.cpp	The test documents small multi-batch and oversized ranges. It removes the half-batch and single-batch chunk sizes. The copyright notice now covers 2024–2026 and includes the NVIDIA affiliates designation.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 3d61b

This updates JSON multi-batch test coverage to retain representative small and oversized ranges while removing redundant cases. No current merge-readiness risk remains.

Suggested reviewers: davidwendt

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: reducing JSON multi-batch test coverage.
Description check	✅ Passed	The description directly explains the removal of redundant middle chunk sizes and the retained representative test cases.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}