MDEV-24625 Part 1: Static Analysis of Error Handling Logic for New Binlog Files

MDEV-24625 showcases that problems in opening the binary log lead to debug assertions that may indicate the server running in an invalid state.

This ticket is a sub-task of the overall problem to perform an initial manual static-analysis (i.e. code-level analysis) of the issue. This analysis will be used in a future task to create MTR tests which verify the expectations set out by the report. The report should track:

1. The functions that open binary logs
1a. What errors can be reported by these functions?
1b. Are there calls that should have error handling but don't?
1c. Are all functions consistent in how they report these errors?

2. What contexts/use cases call into these functions that open binary logs?
2a. How are these errors handled?
2b. Are these errors ever overriden/discarded?
2c. Is error handling consistent between these different use cases?
2d. What are the expected server/transaction states before opening new binary logs?
2e. What are the expected server/transaction states after opening new binary logs?
2f. What are the expected server/transaction states after failing to open a new binary log?