Configuration Validation Fails for 'ignite.expiration' in Ignite 3.0

**Description:**
When using the following configuration in Ignite 3.0:
```
{
ignite{
expiration{
batchSize=1000,
checkFrequency=600000,
parallelismLevel=1
}
}
}
```

**The error occurs:**
```
Caused by: org.apache.ignite.configuration.validation.ConfigurationValidationException: Failed to parse HOCON: 'ignite' configuration doesn't have the 'expiration' sub-configuration
at org.apache.ignite.internal.configuration.ConfigurationDynamicDefaultsPatcherImpl.convertToSuperRoot(ConfigurationDynamicDefaultsPatcherImpl.java:85)
at org.apache.ignite.internal.configuration.ConfigurationDynamicDefaultsPatcherImpl.patchWithDynamicDefaults(ConfigurationDynamicDefaultsPatcherImpl.java:57)
at org.apache.ignite.internal.configuration.storage.LocalFileConfigurationStorage.patch(LocalFileConfigurationStorage.java:159)
at org.apache.ignite.internal.configuration.storage.LocalFileConfigurationStorage.readHoconFromFile(LocalFileConfigurationStorage.java:193)
... 28 more
```

**Environment:**
- Ignite 3.0.0
- JDK 11
- OS: Linux

**Questions**
How can I implement expiration configuration on ignite3.0.0 version？

Start with the HOCON configuration shown in the issue and the stack-trace entries in ConfigurationDynamicDefaultsPatcherImpl.java and LocalFileConfigurationStorage.java. Determine whether ignite.expiration is supported in Ignite 3.0.0 and identify the valid configuration path; done means the expiration settings load without ConfigurationValidationException.

Written by the indexing model from the issue text.