WL#7806: InnoDB: Log-based discovery of built-in tablespaces

Affects: Server-8.0   —   Status: Complete

This is follow-up to
WL#7142 InnoDB: Simplify tablespace discovery during crash recovery

Write MLOG_FILE_NAME for all persistent tablespaces, not only for *.ibd files.
Currently, this includes the following:

• The InnoDB system tablespace (ibdata*)
• The InnoDB undo log tablespaces (undo*)

On startup, the InnoDB system tablespace and the InnoDB redo log will be opened.
If there are redo log records to be applied since the latest checkpoint,
any tablespaces requiring cleanup will be opened and recovered based on
MLOG_FILE_NAME records in the redo log.

If the MLOG_FILE_NAME records for the system tablespace disagree with
the server configuration affecting the data file names for the system
tablespace, recovery will be aborted with an error message, before
applying any redo log.

After recovery, any undo log tablespaces for which no redo log records were
applied will be opened based on existing mechanism. The system tablespace will
remain open at all times.