#2479: Cactus does not check that implementation whose parameters are inherited are active

Cactus does not check that a thorn that implements and implementation whose parameters are shared by an active thorn is also active. Eg the test parfile twopunctures_carpet.par in https://bitbucket.org/einsteintoolkit/einsteininitialdata/src/master/TwoPunctures/test/twopunctures_carpet.par activates Carpet but not InitBase (whose parameters Carpet SHARES). This leads to parameters of a non-active implementation being used.