Can the Fluss cluster change the datalake configuration from the cluster level to the table level?

### Search before asking

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

### Motivation

The datalake configuration of the current Fluss cluster requires specifying datalake.format in server.yml, which means a single Fluss cluster can only use one datalake format. If multiple datalake formats need to be used simultaneously, multiple Fluss clusters must be deployed.

If the datalake configuration is changed from the cluster level to the table level, will a single Fluss cluster be able to support multiple datalake formats simultaneously?

### Solution

_No response_

### Anything else?

_No response_

### Willingness to contribute

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

Start with the current cluster-level datalake.format setting in server.yml and trace how it is applied. Define how a table-level setting would coexist with the existing cluster configuration and verify that one cluster can use multiple datalake formats; the issue names no implementation files or tests.

Written by the indexing model from the issue text.