Fix(Core): Optimize container loading when there are a large number of entities

[stonebuzz]

…f entities

Checklist before requesting a review

Please delete options that are not relevant.

• I have performed a self-review of my code.
• I have added tests (when available) that prove my fix is effective or that my feature works.
• I have updated the CHANGELOG with a short functional description of the fix or new feature.
• This change requires a documentation update.

Description

• It fixes #42749

A user with nearly 5,000 entities is experiencing slowness when opening a ticket containing a container.

They are using a tree view with recursive mode enabled.

Currently, the plugin adds a WHERE clause on entities using all the user’s entities (glpi_active_entities), which significantly impacts performance.

The logic used to verify whether access to the container is authorized has been moved further downstream in order to lighten the SQL query.

It now relies on Session::haveAccessToEntity.

Screenshots (if appropriate):