client: attribute management for open and fsync

Nobody has claimed this yet.

Avoid the conflict on file id. Current implementation generate files id based on
hashcode of file name, conflict happens when two file names are hashed to the same file id.

Provide atomic update on file id. When a file is openned with O_CREAT, the client first
checks if the file is created, then creates a file if it does not exist, or returns error
if O_EXCL is set. These operations needs to be atomic.

During fsync, the final file size should be the largest size (typically in the checkpoint workload)
among the metadata sent by all clients. Current implementation takes the last file size received as the final file size for fsync, which may not be the correct one.

Start by tracing the client paths for open with O_CREAT/O_EXCL and fsync metadata handling, then inspect how file IDs are generated and updated. Done means concurrent file creation is atomic without file-ID conflicts, and fsync uses the largest file size received from clients.

Written by the indexing model from the issue text.