MockMaker : Make sure super constructor gets called when spying

I've noticed a defect : if the same class is mocked and spied on then one of these two scenarios is going to take precedence (it seems to have the same behaviour on MacOSX & Windows but the opposite one on Linux — so if the spied class is generated on MacOSX & Windows it's going to be the mocked one on Linux and opposite). This results in a spy potentially not calling the constructor or a mock potentially calling it.

This patch fixes this issue by moving the logic of returning before calling the super constructor to the runtime, based on the "spy" parameter.