[EPIC] Type safe TableProperties parsing.

### Is your feature request related to a problem or challenge?

Currently when we parse table properties, we parse them manully. Ideally we should be able to pasre `TableProperties` using derived approach as following:
```rust
pub struct TableProperties {
#[key="read.split.target-size"]
#[default(134217728// or some const)]
#[doc("Target size when combining data input splits")]
read_split_size: usize,
....
}
```

### Describe the solution you'd like

_No response_

### Willingness to contribute

I can contribute to this feature independently

Start by locating the current manual parsing implementation for TableProperties and trace how its properties are represented and validated. Compare that flow with the proposed derived approach and identify the required fields, defaults, and documentation; done means TableProperties can be parsed type-safely without losing existing behavior, with tests covering the resulting properties.

Written by the indexing model from the issue text.