Rename (and overhaul?) NodeHiddenStateProjection

[bwaidelich]

As @mhsdesign correctly brought up, the term NodeHiddenState is not in sync with the notion of disabled nodes.

I guess, with the suggestions from #3732 we could that projection into one that calculates "attributes" (or what we end up calling these) for nodes and their descendants, such that instead of

$nodeHiddenStateFinder->findHiddenState();

we could do something like

$nodeAttributeResolver->hasAttribute(NodeAddress $node, 'disabled');

[mhsdesign]

@nezaniel and me discussed to rename the NodeHiddenState directly to NodeRestrictionState so we can later with Neos 9.1 enrich this feature with more than just two states (frontend users and backend users): #3732

[mhsdesign]

We want to move this projection into Neos.Neos to make this less "stable api"

[mhsdesign]

might be solved with the introduction of attributes: #4550

[mhsdesign]

Solved via #4550

$nodeIsDisabled = $node->tags->contain(SubtreeTag::disabled());