Changing values in the stacker has wrong behavior

When changing a value in a StackedConfig it is not written to the source handler of highest priority but instead to the lowest (relevant code and unnecessary reversing). Also in case the reverse parameter is used this is not even considered in the aforementioned reversed iteration. This means that in case the parameter was set to True, the changes are written the other way around.

@todo add examples

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information