After a log file rotates, the new running log outputs some basic server status at the start, e.g. featureCompatibilityVersion, Build Info, Operating System, PID, etc.

We should add the log rotation status of the previously-rotated log to this collection of "header" data in the new log file, so that any issues with rotating the previous log do not depend on access to the rotated log file. For example:

1. Log rotation status (success / failure)
2. Absolute path to rotated log file (example: target=/tmp/mongo-log-rotator-suite-267013706/mongo-log-rotator_audit.log.2022-01-19T17-50-55)
3. Any minor error messages (more useful with recent improvements in log rotation error messages)