Autoresearch for go2 blueprint cpu/sys footprint

deploy go2 big office replay, measuring cpu/sys time

`time uv run dimos --replay --viewer=none --replay-dir=unitree_go2_bigoffice run unitree-go2`

ask autoresearch to optimize cpu/sys usage

make sure that replay has some self-validation, for example makes sure none of the messages in the LCM pipeline have changed (run a recorder for example, compare with original recording)