Never direct users towards using rr.log_components

[teh-cmc]

rr.log_components is a clunky implementation detail, at best. Users should be directed towards rr.log, always.

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!
• If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

To deploy documentation changes immediately after merging this PR, add the deploy docs label.

[github-actions]

Latest documentation preview deployed successfully.

Result	Commit	Link
✅	6a7bdd2	https://landing-fogfrohde-rerun.vercel.app/docs

^{Note: This comment is updated whenever you push a commit.}

[teh-cmc]

@rerun-bot full-check

[github-actions]

Started a full build: https://github.com/rerun-io/rerun/actions/runs/11841295496

[Wumpf]

right, we made log handle this a while ago. What are cases where one would still need it actually? Should we deprecate it?

[teh-cmc]

right, we made log handle this a while ago. What are cases where one would still need it actually? Should we deprecate it?

I thought about deprecating it at one point, but then realized that we ourselves ultimately delegate to it in order to actually log stuff... but now that I'm taking a closer look, it seems to be the exact same code as log() 🤦

I'll take a closer look -- if it is indeed the exact same code, I'll deprecate it too.

[teh-cmc]

Nuh-uh, nevermind, they're not even close to the same, and it even makes sense as is 👍