O_DSYNC setting bug. about wasm-micro-runtime

[TianlongLiang]

Similar to #3565, O_DSYNC is not part of the file status flags that can be modified using fcntl. You can only set its value when first set it with open

[TianlongLiang]

Refer to the manual of syscall open and fcntl:

In open

       In addition, zero or more file creation flags and file status
       flags can be bitwise ORed in flags.  The file creation flags are
       O_CLOEXEC, O_CREAT, O_DIRECTORY, O_EXCL, O_NOCTTY, O_NOFOLLOW,
       O_TMPFILE, and O_TRUNC.  The file status flags are all of the
       remaining flags listed below.  The distinction between these two
       groups of flags is that the file creation flags affect the
       semantics of the open operation itself, while the file status
       flags affect the semantics of subsequent I/O operations.  **The
       file status flags can be retrieved and (in some cases) modified**;
       see [fcntl(2)](https://man7.org/linux/man-pages/man2/fcntl.2.html) for details.

In fcntl

       F_SETFL (int)
              Set the file status flags to the value specified by arg.
              File access mode (O_RDONLY, O_WRONLY, O_RDWR) and file
              creation flags (i.e., O_CREAT, O_EXCL, O_NOCTTY, O_TRUNC)
              in arg are ignored.  On Linux, this operation can change
              only the O_APPEND, O_ASYNC, O_DIRECT, O_NOATIME, and
              O_NONBLOCK flags.  It is not possible to change the
              O_DSYNC and O_SYNC flags; see BUGS, below.