Switch Flight Software (FW_ASSERT) To "Clickable" Format

[LeStarch]

In the UT assert messages, we switched to a clickable format such that when running the UTs in appropriate environments (e.g. inside an IDE) one can quickly navigate to the offending line. This works quite well given that UTs are often run on development machines. Here we are discussing output for console messages only not events.

The next question is should we adjust the format of the flight software asserts. This is a bit more nuanced as flight software can but often does not run on development machines. This is complicated by the fact that flight software often does not print the file name, but rather file hashes, partial paths, etc.

On the advantage side, this reduces the assert string length by multiple characters.

Clickable Format: <file path / hash >:<line>

/path/to/my/file.cpp:123
realtive/myfiel.cpp:123
0x00abcdef:123

Existing Format: File: file path / hash> Line: <line>

File: /path/to/my/file.cpp Line: 123
File: realtive/myfiel.cpp Line: 123
File: 0x00abcdef Line: 123

Note: I am trying out the polls feature to gather thoughts not a final decision on the implementation.