feat(config): warn unrecognized field instead of panicking

[Gun9niR]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

For backward compatibility, when we deprecate a config it should still be acceptable from the config file. A demo:

#[test]
fn test() {
    let c: RwConfig = toml::from_str(
        r#"
        ccc = "a"
        
        [batch]
        aaa = "??"

        [storage.file_cache]
        bbb = 1

        [storage]
        sstable_size_mb = 256
    "#,
    )
    .unwrap();
    warn_unrecognized_fields(&c);
}

Output is

unrecognized fields in config: ["ccc"]
unrecognized fields in config section [batch]: ["aaa"]
unrecognized fields in config section [storage.file_cache]: ["bbb"]

Checklist For Contributors

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
• All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

• I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

• My PR DOES NOT contain user-facing changes.

Click here for Documentation

Types of user-facing changes

Please keep the types that apply to your changes, and remove the others.

• Installation and deployment
• Connector (sources & sinks)
• SQL commands, functions, and operators
• RisingWave cluster configuration changes
• Other (please specify in the release note below)

Release note

Unrecognized fields in the configuration file will generate a warning log instead of causing panic.

[codecov]

Codecov Report

Merging #8325 (608a910) into main (e6f2561) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #8325      +/-   ##
==========================================
- Coverage   71.62%   71.62%   -0.01%     
==========================================
  Files        1135     1135              
  Lines      185458   185468      +10     
==========================================
- Hits       132835   132833       -2     
- Misses      52623    52635      +12     

Flag	Coverage Δ
rust	71.62% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/common/src/config.rs	88.20% <0.00%> (-4.03%)	⬇️
src/meta/src/hummock/mock_hummock_meta_client.rs	64.43% <0.00%> (-1.04%)	⬇️
src/object_store/src/object/mod.rs	47.87% <0.00%> (-0.21%)	⬇️
src/storage/src/hummock/compactor/mod.rs	80.19% <0.00%> (-0.20%)	⬇️
src/common/src/cache.rs	97.15% <0.00%> (-0.11%)	⬇️
src/meta/src/hummock/manager/mod.rs	78.83% <0.00%> (-0.07%)	⬇️
src/storage/src/hummock/sstable_store.rs	64.35% <0.00%> (ø)
src/stream/src/executor/aggregation/minput.rs	96.27% <0.00%> (+0.10%)	⬆️
src/common/src/types/ordered_float.rs	32.81% <0.00%> (+0.19%)	⬆️
src/storage/src/hummock/compactor/iterator.rs	96.68% <0.00%> (+0.27%)	⬆️
... and 1 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[BugenZhao]

Very intelligent. 😄 serde-rs/serde#941

[BugenZhao]

We're now using the GitHub merge queue. 🥺