Real "private area" pages with editorial content

### User Story

As an e-commerce manager, I want to create a private area tree of pages to be accessible according to some logic based on user attribute. These pages must editable as all other content pages of the site allowing the editorial team to add component by drag&drop.

### Description & Motivation
Assuming that the user data received from Magento has some custom option defining some user-specific attribute, it would useful if editor team can create pages in AEM as the normally do and then applying some kind of tagging/ACL in order to let the page tree be visible only to users with defined attribute.

For example the e-commerce users can be divided in 3 different type: standard, advanced and professional user.
Let's assume each of this type has an attribute on [customer query](https://devdocs.magento.com/guides/v2.4/graphql/queries/customer.html), named for example **userType**.
On author will be created the following tree:
- /content/project/us/en/private-area
-- standard-user
-- advanced-user
-- professional-user

and each of this node will have its own pages, for example for standard-user

- dashboard
- account-details

while for advanced-user
- dahsboard
- account-details
- subscriptions
- support

Only users with **userType=advanced-user** will be able to access to /content/project/us/en/private-area/advanced-user.

### Acceptance Criteria
- To be able to use customer attributes to restrict access to subtree of the site
- The subtree must customisable by editorial teams as normal content pages

The issue does not identify files, tests, or an entry point to inspect. Start by clarifying the access-control design and how customer attributes map to editable page subtrees; done means editorial teams can configure such pages and users can access only the subtree allowed by their attribute.

Written by the indexing model from the issue text.