Fixing Redo Log file open mode from InnoDB Clone

Summary:
This diff fixes https://bugs.mysql.com/bug.php?id=97755
Prior to this diff, at clone plugin file sync phase, it opened
InnoDB redo log file with the same file option as data files,
not redo log file specific options. This particularly caused
problems with innodb_flush_method=O_DIRECT. InnoDB redo log files
are always opened without O_DIRECT. However prior to this diff,
clone plugin opened InnoDB redo log files with O_DIRECT (since
it referred data file option) and hit offset errors.
This diff fixes it -- using redo log specific option, which means
O_DIRECT is not passed, so no offset error happens anymore.

Reviewed By: hermanlee

Differential Revision: D37231218

fbshipit-source-id: 1caa4f3f8d762055b3df6768f5fad575e3d184c2

Author: yoshinorim

storage/innobase/clone/clone0apply.cc

@@ -1194,15 +1194,16 @@ int Clone_Snapshot::init_apply_state(Clone_Desc_State *state_desc) {
 
 int Clone_Snapshot::extend_and_flush_files(bool flush_redo) {
   auto &file_vector = (flush_redo) ? m_redo_file_vector : m_data_file_vector;
+  auto file_type = flush_redo ? OS_CLONE_LOG_FILE : OS_CLONE_DATA_FILE;
 
   for (auto file_meta : file_vector) {
     char errbuf[MYSYS_STRERROR_SIZE];
     bool success = true;
 
     auto file =
         os_file_create(innodb_clone_file_key, file_meta->m_file_name,
-                       OS_FILE_OPEN | OS_FILE_ON_ERROR_NO_EXIT, OS_FILE_NORMAL,
-                       OS_CLONE_DATA_FILE, false, &success);
+                               OS_FILE_OPEN | OS_FILE_ON_ERROR_NO_EXIT,
+                               OS_FILE_NORMAL, file_type, false, &success);
 
     if (!success) {
       my_error(ER_CANT_OPEN_FILE, MYF(0), file_meta->m_file_name, errno,