Improve Automatic Recovery detection of a mismatched file caused by copying a file outside the server
Before running automatic recovery, if a file is copied to the server's data directory, overwriting another file having a different file name, in some cases automatic recovery doesn't detect that the file is not the proper file. Two changes were made to automatic recovery to handle cases that involved the rename of a file:
The recovery step that opens the file by its renamed filename ignored a file ID mismatch. Now we check if the file ID mismatch is explained by a subsequent transaction-dependent operation such as a file create or a rename of another file name to that file name with that file ID. If so, we allow recovery to continue; if not, we log the message "Detected file ID mismatch file:" and the file name to CTSTATUS.FCS and fail recovery with a file ID mismatch error, 499.
If an undo of a rename fails, recovery fails (previously, recovery proceeded in this situation).
