Respect the log.* config from the table level options

### Search before asking

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

### Motivation

I found that `log.segment.file-size` currently only respects server-level configurations and is ignored when defined at the table level. I would like to propose a mechanism that allows the system to prioritize table-specific configurations if they exist, falling back to the global server options only as a default. This would provide better flexibility for handling tables with unique throughput or storage requirements.

### Solution

_No response_

### Anything else?

_No response_

### Willingness to contribute

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

Start by locating where the log.segment.file-size option is read for table-level options and where server-level configurations are used as defaults. Trace the configuration resolution path and determine how table-specific values should take precedence, then verify that the server setting remains the fallback for tables without an override.

Written by the indexing model from the issue text.