fix(services/goosefs): skip CreateDirectory when rename parent already exists

[XuQianJin-Stars]

Which issue does this PR close?

Closes #.

Rationale for this change

GooseFS write-via-temp publishes with rename(tmp → final) in the same parent directory. CreateFile(recursive) on the temp path already creates that parent, but GoosefsCore::rename still called create_directory(parent, recursive) whenever the destination was missing.

The comment treated that RPC as a cheap Master no-op. Under CACHE_THROUGH, Master still sync-persists the directory to UFS, so an already-existing parent pays a full object-store round-trip (about 45–55ms in our CosN measurements; four small Lance files add ~0.19s).

flowchart TD
  start[rename tmp to final]
  stat[get_status dst]
  exists{dst exists?}
  dir{dst is directory?}
  overwrite{if_not_exists?}
  del[delete dst]
  rename1[Master rename]
  ok{rename Ok?}
  src{source still exists?}
  mkdir[create_directory parent]
  rename2[Master rename retry]
  done[done]
  fail[return error]
  cnm[ConditionNotMatch]

  start --> stat
  stat --> exists
  exists -->|yes| dir
  dir -->|yes| fail
  dir -->|no| overwrite
  overwrite -->|true| cnm
  overwrite -->|false| del --> rename1
  exists -->|NotFound| rename1
  rename1 --> ok
  ok -->|yes| done
  ok -->|NotFound| src
  src -->|no| fail
  src -->|yes| mkdir --> rename2 --> done

Loading