Implement basic logging functionality

[celery6]

some notes

• only 1 log function can run at once, so logging is blocking up to 50 ticks (arbitrary number for now)
  • logs can be printed out of order cuz tasks are unblocked by priority not time. however the timestamp is acquired before waiting, so actual order can be post-processed if needed
• still needs more thinking about full buffer edge cases for protecting against out of bounds and overwriting !!!!!!!! Are there any glaring issues currently?
• since the logger function uses snprintf, all tasks that log will get stack eaten by snprintf :( should do better stack usage analysis someday to make sure this is fine...
• not sure if each buffer itself should be protected by a mutex or if the isFull flag is enough. I think using per-buffer mutexes would still require the isFull flag due to the handoff between log funcs and dump queue (something needs to guard a full buffer while its waiting to be dumped). idk

[Joe-Joe-Joe-Joe]

Have you tested on the hardware yet?

[celery6]

Tested latest changes, works well. Tested spamming logs in all tasks and buffers don't get full with the current osDelay(1000), but they do get full with shorter osDelays. To be optimized later ig!

merged master but didn't initialize task in main.

[Joe-Joe-Joe-Joe]

When you say "buffers get full" I'm assuming what you mean is that buffers fill up faster than they can be dumped over UART?

[celery6]

Yes

[Joe-Joe-Joe-Joe]

try bumping baud rate to 500000 I know for a fact the chip supports it, idk if the programmer will bottleneck us there tho