Tracking issue for the complete "custom user data" story as a whole, i.e.:

• The API uses an as_components() kind of model:
  • It is used by builtin archetypes and components to drive their serialization.
  • It can be easily implemented in user code, allowing for the creation of new archetypes & components without the IDL.
• Indicator components are materialized in the type system, and can be instantiated in user code with arbitrary names.
• The API provides a way to extend/wrap/embed builtin archetypes and components from user code.
  • E.g. to add a couple custom components to the existing builtin point cloud archetype.
• We provide a custom_data example that shows the story as whole.

In general, we should strive to avoid the old "user code" vs. "internal code" dichotomy: user code should be able to do everything that internal code does without having to jump through hoops and without any kind of performance penalties, i.e. there is no such thing as internal code.
This mostly naturally falls out of the as_components() model, and with a bit of care should be easily attainable in all SDKs.

• Archetypes should implement as_components #3103
• First-class citizenry for indicator components #3159
• Extending builtin archetypes & components:
  • Rust
  • C++
  • Python
• custom_data example
  • Rust
  • C++
  • Python