Rerun Bridge should reconstruct the tf tree automatically

This is an ok first issue, but a bit involved.

The way rerun deals with tf and ros deals with tf is not the same

https://rerun.io/docs/concepts/logging-and-ingestion/transforms

we have a service that reconstructs and provides ros like tf tree @ dimos/protocol/tf/tf.py

rerun bridge should run dimos tf service internally (like modules do) subsribe to updates (add subscriptions/observables to tf service btw)

and it should correctly configure rerun TFs for entities drawn.

for now this is hacked, and unitree go2 blueprint hardcodes this
dimos/robot/unitree/go2/blueprints/basic/unitree_go2_basic.py

running rerun-bridge independantly has a broken tf tree, running rerun-bridge should have a correct TF tree and we shouldn't need custom config in unitree blueprints

Synced from DIM-721 by summer

Start with dimos/protocol/tf/tf.py to understand the existing ROS-like TF reconstruction service, then inspect the rerun-bridge entry point and its relationship to service modules. Compare this with dimos/robot/unitree/go2/blueprints/basic/unitree_go2_basic.py and the transforms documentation. Done means running rerun-bridge independently produces a correct TF tree without custom configuration in the Unitree Go2 blueprint.