fix: increase telemetry-sidecar CPU

[mo-getter]

Rationale

We have observed that some of the telemetry-sidecar containers use near their full 100m cpu limit.

Credit: @kevin-dimichel

Review Priority

• high
• medium
• low

Changes

• docker compose: bump cpu reservation/limit to 200m for teams-plugins-telemetry-common
• helm: bump all telemetry-sidecars to 200m
• update docs accordingly

Checklist

• This PR maintains parity between Docker Compose and Helm

Testing

Local helm template

[coderabbitai]

Looking for one thing? Review this PR in Change Stack to search files, summaries, diffs, and code without losing your place.

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dd84b06b-dd73-49e3-9b06-faf0f938f14c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

This PR updates telemetry sidecar resource documentation across Docker and Helm deployment targets. CPU request/limit values are increased from 100m to 200m per sidecar, default sidecar counts are adjusted, and resource impact totals are recalculated in deployment upgrade guides and Helm values documentation.

Changes

Telemetry Sidecar Resources

Layer / File(s)	Summary
Telemetry sidecar resource requirements across deployment targets docker/docs/upgrading.md, helm/docs/upgrading.md, helm/fiftyone-teams-app/README.md	Updated telemetry sidecar resource impact estimates across Docker and Helm documentation: per-sidecar CPU increased from 100m to 200m, default sidecar counts adjusted, and total CPU and memory impact recalculated in upgrade guides and values documentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A sidecar feast with more muscle and might,
Two hundred millicores shining so bright,
Through Docker and Helm, the docs now align,
Resource requests refreshed—telemetry by design!
✨🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: increasing telemetry-sidecar CPU allocations from 100m to 200m.
Description check	✅ Passed	The PR description includes all required sections: rationale, changes, checklist for parity, and testing. All sections are adequately filled with relevant details.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/telemetry-cpu-limit

---

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