Provide AnyValues helpers in Rust SDK

[grtlr]

Related

• Part of Tagged components #6889.
• Closes AnyValues should use argument names to set archetype_field_name metadata #9906.
• Part of Add AnyValues wrapper to C++ API #9340.

What

This PR does multiple things:

• Works towards providing a common AnyValues interface that is similar across Python 🐍 , C++ 🌊 , and Rust 🦀 SDKs (so far we only have AnyValues in Python).
• By using the new AnyValues we ensure that more of the logged data is actually tagged.

[github-actions]

Web viewer built successfully. If applicable, you should also test it:

• I have tested the web viewer

Result	Commit	Link	Manifest
✅	f59fbb9	https://rerun.io/viewer/pr/10074	+nightly +main

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

[emilk]

If we use impl Into<ArrayRef> as the argument type, maybe we can get rid of the Arc::new here?

[grtlr]

I tried this, but unfortunately could not get the compiler to comply.

[emilk]

I think most users will first grab for AnyValues::new(), and maybe not even realize there is a AnyValues::default(), and so they will wonder what they should pick for archetype name.

So I suggest we do builder pattern all the way instead:

AnyValues::new().with_field(…)
// vs
AnyValues::new().with_archtype_name(…).with_field(…)

or alternatively use a more verbose ctor name:

AnyValues::new().with_field(…)
// vs
AnyValues::from_archtype_name(…).with_field(…)

[grtlr]

I deliberately made that choice to nudge users to provide an archetype name, which should be good practice going forward as it helps with uniquely identifying the data going forward.

[github-actions]

Latest documentation preview deployed successfully.

Result	Commit	Link
✅	681dbc6	https://landing-ik6jd35fu-rerun.vercel.app/docs

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