Don't mark the tree dirty when active changes
The tree doesn't change so there's no reason to trigger a full update
when a global state update is enough.
NOTE: This change also exposes another bug that was hidden due to the
tree always being reindexed when a node changed it's active state.
The bug was caught by the tst_RenderControl test and was due to
GlobalStateResult never having it's activeDirty bit set.
Pick-to: 6.12 6.11
Change-Id: I4d83473ada30a98e5cc42c18ae0c195231cc1d24
Reviewed-by: Andy Nichols <andy.nichols@qt.io>