Deal with issues when the disk is full

Check: https://github.com/bluerobotics/BlueOS/issues/2327, https://github.com/bluerobotics/BlueOS/issues/2323, https://github.com/bluerobotics/BlueOS/issues/2326, https://github.com/bluerobotics/BlueOS/issues/1015

The docker is able to start, but everything after that just results in unstable behavior.
Some points that you suggested are already available as issues, others are relevant to recover the system.
- [x] We should delete old logs when doing the rotation and noticing the the disk space is almost full.
- [ ] We should stop logging if the disk space is almost full.
- This conflicts with rotation configuration in loguru
- [ ] We should clean up old dockers that are not being used.
- [ ] We should clean up old docker artifacts that are not being used.
- [ ] We should allow user to delete all unused docker images.
- [ ] We should warn the user though cockpit that the companion computer is almost full in disk.
- [ ] We should erase older tlog or bin files if the disk is almost full.
- #1257
- [ ] We should warn the user though BlueOS header that the disk is almost full and in critical state.
- [ ] We **may** not allow the user to arm the vehicle if the disk is almost full.
- [ ] We **may** do some of this steps automatically to try to recover the system once it starts.
- [ ] We **may** need a page like [filelight](https://apps.kde.org/pt-br/filelight/) on BlueOS to help identify the root of such problems.
- [x] We should limit journald max size

_Originally posted by @patrickelectric in https://github.com/bluerobotics/BlueOS/issues/2325#issuecomment-1902117968_