Update ArgosLogger to interact with NT & On-Robot Telem Logging

[Litemage]

Give the option for subsystems using the currently implemented ArgosLogger to post error messages to network tables (if prompted) this offers a less-permanent solution to logging directly to the robot, while also being able to see these errors after they happen.

• Maybe under the tag /robotErrors/$TAG/(Info || Warning || Errors)/?

Also give the option for logging to the robot on a file although this feature should only be used rarely, if ever, as these files can clog up the /hom/lvuser if not manually deleted.

Also while we're here, add a third log level for Warnings and append the tags _WARN and _INFO to the end of logged messages

These changes may also facilitate the need for std::format being used, which would be a cleaner implementaton.

[Litemage]

Made some headway in 2299815 (Still needs validated)
Ended up axing NT because the implementation necessary for it just doesn't seem practical given the end result. Looks like it would have been necessary to store the WHOLE array of messages for each log level for each logging object.... yea memory hog waiting to happen.

[Litemage]

Backlogging until I can come up with something more reliable, print to stdout is flakey at best, NT logging is axed, and I still need to validate any sort of file system logging.