Rethink logging for Fort 2

Rethink logging for Fort 2

- Rename "operation logs" to just "logs"
- Rename "validation logs" to "report"

Rationale: Logging is meant for sysadmin consumption.
Sysadmins don't care if some RPKI objects need to be thrown away.

- Logs can be sent to std streams, files or syslog. Reports only go to files.
  Logs and reports go to different files (because they're different things).
- Subdivide DEBUG into TRC, CLT and DBG.

"TRC"s (traces) are algorithm steps as they happen.
"CLT"s (clutters) are detailed information about what's happening.
"DBG"s are just temporal debugging prints.

- Rename CRIT into PANIC.
- Subdivide ERR ento ERR and CRIT.

"ERR"s are normal, expected errors.
"CRIT"s (criticals) are unexpected (but recoverable) errors.

- Apply #121: Redirect WRNs and ERRs to reports during validation cycles.

Logs actually still get WRNs and ERRs, but they're downgraded to TRCs.

Still TODO:

- Configuration layer has not been updated
- Reports don't print offending file names