Well, as we set the parameter names on the configurations, we can later read them, and consistency is guaranteed without code duplication (as i said before about `setKeys()`)

I like the approach of having small components (like our Configurators), because we can combine them freely.
We don't have to combine them always by creating a new class.
The main reason why i create classes is to have a testable, reusable, encapsulated component, and i don't think i can reuse much of a new Configurator class here, as is would be very specify to SurvivalAnalysis.
It can be an inner class (as CensoringColumnConfigurator). I didn't do it because initially there was not much logic to encapsulate.

A good part of my code there was a kind of 'superstition', namely the logic for choosing the missingValueAction, and setting it in both the `OptionalBinningColumnConfigurator` and its inner configurator.
I had the impression that something there was not working, and at the time i didn't realize i could never match exactly the outputFiles. So some code here can certainly go away.