bluerobotics
core: move setup_ssh() over to startup_blueos_update
not tested.
The issue here is that the ssh setup was being done after blueos_startup_update, when commander started up. This meant it would always fail on the first boot, to succeed later on after commander ran at least once.
fix #3038
just rebased and re-tested by deleting the content of /home/pi/.ssh/authorized_keys on the host, and the keys on the container at
/root/.config/.ssh and rebooting. everything seems in order.
We probably need to backport this to stable since our README states the following
armv8/arm64: This is used by more recent, high-performance devices. You can run BlueOS on a Raspberry Pi 4, or in a computer with Apple Silicon.
But on PI4 blueos_startup_update cannot apply required patches to the /boot/firmware/config.txt file resulting in autopilot manager not detecting navigator board on the first boot, only after a reboot navigator will appears as a valid board.
