[Issue] Add ACL role ID to category tree cache id

[ghost]

This issue is automatically created based on existing pull request: #27429: Add ACL role ID to category tree cache id

---

Preconditions: (*)

When an admin user views a product's category tree (by editing a product), the category tree is cached with an ID akin to CATALOG_PRODUCT_CATEGORY_TREE_0_ (the $filter option is not used in the Magento codebase).

This is not compatible with admin users that have limited Role Scopes. If the first admin user to view a product category tree has access to all websites (e.g. Administrator), this then caches the full category tree for all websites. Then the limited admin user will also see this full category tree even if they should be limited to a single website's category tree. Similarly, if the limited admin user views the category tree after the block cache is cleaned, the Administrator user will only see a limited category tree.

This pull request adds the admin's user's ACL role ID to the cache ID. This is probably about as performant as we can get.

Steps to reproduce: (*)

1. Create a product, category -> Default Category/default and assign it to Main Website Store;
2. Create a new root category with child (Second Category/second_category for ex.);
   
3. Create a new Website, Store, Store view ( Second Website, Second Website Store, Second Website Store view) and set Second Category as default;
   
4. Assign a few products to the new website and new category;
5. Create a new website-limited admin user with only access to the new website.
   ⭕ Admin_GWS functionality
   
6. Clean block_html cache and view a product's category tree as an Administrator admin user;
7. Log in as the website-limited admin user and view the category tree for any product.

Actual Result: (*)

✖️ The categories from Main Website is shown

Expected Result: (*)

✔️ user should only see a limited category tree

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[sdzhepa]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @sdzhepa. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @sdzhepa, here is your Magento instance.
Admin access: https://i-28306-2-4-develop.instances.magento-community.engineering/admin_4b6a
Login: 27a7bf0e Password: 163dd4f0776e
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-34948 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @m2-backlog[bot]. Thank you for your report.
The issue has been fixed in #27429 by @quangdo-aligent in 2.4-develop branch
Related commit(s):

• 54a11eb67d5ad3b0f2ca0160dcfa936d50b44d33
• f1c8ad56edcad49fd51288e3a0dbf2df74505df5
• 207a44956715bee23dbd7c0ded5735283299f9cc
• 61f847ec3edbf7c91ae7158d81778109c0821fbc
• 5a4e93f80eee1d37c63243d4e99d947aa8465a96
• e5b64f533b984063d9e735cf6f2b485fca6b721b
• 06d3e3aa19f2a51332996416a38725d03d21be05
• 179a72ff4736c51d6189c4422f4245dacb800004
• a09627037573662071d47fa0d022bd4035e45818

The fix will be available with the upcoming 2.4.1 release.