What's the idea behind splitting configuration across multiple files, when in the end, most of them are in fact children of the framework key?

A (quite) basic installation of Symfony 7.4 now creates those 19 files inside config/packages:

1. asset_mapper.yaml *
2. cache.yaml *
3. csrf.yaml *
4. debug.yaml
5. doctrine.yaml
6. doctrine_migrations.yaml
7. framework.yaml *
8. mailer.yaml *
9. messenger.yaml *
10. monolog.yaml
11. notifier.yaml *
12. property_info.yaml *
13. routing.yaml *
14. security.yaml
15. translation.yaml *
16. twig.yaml
17. ux_turbo.yaml *
18. validator.yaml *
19. web_profiler.yaml (*)

Those 12-13 with an asterisk * are just contributing to framework. And many of them don't contain much. So I'm suggesting to merge all these into framework.php. This would reduce the total number of files to 7-8.

The drawback of splitting them is that you can never be sure if some setting isn't overridden somewhere else. E.g. I just noticed that in my project I have email_validation_mode twice (framework.php and validator.php).