In WT-7902 session_api.c:session_alter was modified to perform a system-wide checkpoint if the alter operation returned EBUSY and then try again. That change moved most of the original alter code into session_alter_internal.

The API macro calls moved with it and that is a bug. The API macro calls SESSION_API_CONF, API_RET_NOTFOUND_MAP should be at the top-level in session_alter.

This has a real impact because if the checkpoint/retry case is taken then the checkpoint is done without any of the session name information. Then CHECKPOINT_PROGRESS messages are ambiguous. The message and session contain the default session name and then there's no way to know what API the message is coming from.