Refactor: Make transform configurations explicit, rework parsing of transforms

[Beetelbrox]

Closes: #122

Description

As most entities in the project transforms were storing their configuration in a dictionary defined in RbtParamHandler, several steps higher in the inheritance hierarchy. This made it very difficult to understand which configuration each transform needed, which ones were the default values, and which value was being used at any given point in time.

Proposed changes

To address the above explained we've made the parameters required by each one of the transforms explicit. Now each transform defines a Config struct with their respective configuration and transform constructors now accept this configuration instead of having to set arbitrary parameters passing strings as we did before. The TransformFactory builds transforms by grabbing the necessary values from the ParameterSource internal state and building the appropriate config for each transform, explicitly stating which fields are needed instead of dynamically iterating through everything as we did before