HW/LW mixing code handles invalid "apply shape" requests

Currently HW/LW mixing code handles invalid "apply shape" requests. That is, if the component is valid and the direct container of the component is valid but one of other (non-direct) ancestors of the component is invalid, then HW/LW mixing code will proceed with the "apply shape" request and will set the shape to the component.

HW/LW mixing code in 6u12 b02 ignores such invalid "apply shape" requests. A number of high-priority regressions (6777348, 6777655) is a result of the behaviour. It's a future change in the HW/LW mixing code in 6u12 b03 - take into account such invalid "apply shape" requests.

The invalid requests are potentially risky and may lead to unexpected bugs in AWT "mixing" application. The change requets will cover the cases.