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>
commit814708b0b5bea0a45d96c638e6095c9007f9a776
parent135b9f2d4fa967179b76c5f57cc766376526eb46
authorChristian Strømme <christian.stromme@qt.io>
committerChristian Strømme <christian.stromme@qt.io>
commit timeWed, 3 Jun 2026 09:59:11 +0000