[Feature] Improve the tryCommitOnce behavior in FileStoreCommitImpl

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.

### Motivation

When using dedicated compactions in production, we've found the write only job and compact job will failover every 2 or 3 days even if the remote filesystem support atomic rename operation.

The main cause is the FileAlreadyExistsException:

Checking with recent Hadoop API Rename implementation, we found the rename api will return FileAlreadyExistsException for rename api instead of false by default.
https://github.com/apache/hadoop/blob/branch-3.3.6/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirRenameOp.java

IMHO, this can be improved by catch certain exceptions in tryCommitOnce and return false to upper caller.

### Solution

_No response_

### Anything else?

_No response_

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Start by locating FileStoreCommitImpl.tryCommitOnce and the upper caller that handles its result. Compare the remote filesystem rename behavior described in the issue with the current exception path; done means the relevant FileAlreadyExistsException case is handled so the caller receives false instead of the job failing over.

Written by the indexing model from the issue text.