Make PANDA startup quieter

[lacraig2]

This PR changes callbacks.c to use the LOG_* format (LOG_ERROR, LOG_WARNING, etc).

It also makes PANDA somewhat quieter by default with LOG formats that won't necessarily be seen for most items if PANDA's debug mode isn't set quite low.

[AndrewFasano]

So long as LOG_ERROR shows up by default (or maybe just always? Would be awkward to not print some of those errors) this looks great to me.

[lacraig2]

Yes. The default log level does show LOG_ERROR

[AndrewFasano]

@lacraig2 do you think we could silence more of these, either by reducing log level or changing what we log with pypanda?

I'm looking to silence this output from pypanda where I load syscalls2 and OSI

PANDA[core]:os_familyno=2 bits=32 os_details=generic
PANDA[syscalls2]:using profile for linux arm
PANDA[osi_linux]:W> failed to read task.switch_task_hook_addr
PANDA[osi_linux]:W> kernelinfo bytes [20-23] not read

[lacraig2]

@AndrewFasano are you looking for a way to silence these generally or in a specific use case?

If you're willing to accept the latter we might consider building out an API around the LOG_[LEVEL]_FILE macros that let those be set dynamically and directed to a file.

panda/panda/include/panda/debug.h

Line 73 in 1d0069e

#if !defined(PANDA_ERROR_FILE)

[AndrewFasano]

I think I'd like to either
A) Modify this code so it's not logging for my specific use case, or
B) Make it more configurable

These logs aren't really important warnings so I'm not too opposed to option A - I think all 4 of these messages could be logged at the debug level

[lacraig2]

I think that 3 of 4 of those messages could be debug level.

The one that perhaps shouldn't be is:

PANDA[osi_linux]:W> failed to read task.switch_task_hook_addr

I could see a case for the optional fields (like this one) being at the debug level.

I do think B makes sense in general.