MR: Reduce the memory footprint of the component tree

Currently we are parsing down big objects which get watchers, etc. assigned only for actually using 1-2 params somewhere in a component. So we should try to organise it better and only parse ID's, values down the tree so we have less big objects + arrays assigned to components. As we can see in the tree below the creation of components is currently the biggest bottleneck which leads to memory over consumption and also huge CPU spikes.

Test Run locally with a big MR with 58 changed files with 1229 additions and 615 deletions

Switching Discussion -> Changes: Run 1 BE : 5.68 sec FE Component Tree Creation : 25.6 sec FE Overall : 30 sec

Run 2 BE : 3.97 sec FE Component Tree Creation : 29.25 sec FE Overall : 34.5 sec