Make exported journalctl logs less verbose and always display everything (#2101)

## Description

There was a recent occurance of journalctl logs saying something like
`[66B blob data]`. We don't log anything binary, so journalctl might be
hiding some lines, thinking they're actually binary data when they're
actually plain text. Use `-a` to always log everything. If it's binary
data anyways, we'll want to know what it is anyways. Use `--output cat`
because we output our own timestamps and we don't want journalctl's own
timestamping. Filter the output through `sed` to remove ANSI color codes
to make reading logs easier.

## Meta

Merge checklist:
- [x] Pull Request title is [short, imperative
summary](https://cbea.ms/git-commit/) of proposed changes
- [x] The description documents the _what_ and _why_
- [x] If this PR changes behavior or adds a feature, user documentation
is updated
- [ ] If this PR touches photon-serde, all messages have been
regenerated and hashes have not changed unexpectedly
- [ ] If this PR touches configuration, this is backwards compatible
with settings back to v2025.3.2
- [ ] If this PR touches pipeline settings or anything related to data
exchange, the frontend typing is updated
- [ ] If this PR addresses a bug, a regression test for it is added

docs/source/docs/troubleshooting/unix-commands.md

@@ -122,11 +122,13 @@ systemctl status photonvision
 View the PhotonVision logs:
 
 ```
-journalctl -u photonvision
+journalctl --output cat -u photonvision
 ```
 
 View the PhotonVision logs in real-time:
 
 ```
-journalctl -u photonvision -f
+journalctl --output cat -u photonvision -f
 ```
+
+`--output cat` is used to prevent journalctl from printing its own timestamps, because we log our own timestamps.