docs: update usage data

[kanoru3101]

What/Why/How?

Added usage data and product metrics that was used

Reference

Testing

Screenshots (optional)

Check yourself

• Code changed? - Tested with Redoc/Realm/Reunite (internal)
• All new/updated code is covered by tests
• New package installed? - Tested in different environments (browser/node)
• Documentation update considered

Security

• The security impact of the change has been considered
• Code follows company security practices and guidelines

---

Note

Low Risk
Documentation-only change that updates the listed telemetry fields; no runtime behavior or data handling code is modified.

Overview
Updates docs/@v2/usage-data.md to clarify what anonymized usage data Redocly CLI collects, adding items like login state, additional environment variables (CI), API spec type/version, and Arazzo x-security auth types.

^{Written by Cursor Bugbot for commit e2dfc24. This will update automatically on new commits. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: e2dfc24

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	79.65% (🎯 79%)	6588 / 8271
🔵	Statements	79.11% (🎯 78%)	6813 / 8611
🔵	Functions	82.96% (🎯 82%)	1344 / 1620
🔵	Branches	71.56% (🎯 71%)	4507 / 6298

File Coverage

No changed files found.

Generated in workflow #9239 for commit e2dfc24 by the Vitest Coverage Report Action

[github-actions]

CLI Version	Mean Time ± Std Dev (s)	Relative Performance (Lower is Faster)
cli-latest	3.460s ± 0.031s	▓ 1.01x
cli-next	3.435s ± 0.021s	▓ 1.00x (Fastest)