Query for retrieving entities with ready updates should be preventing access check

The changes from patch #2 are also included in Drupal 10 compatibility issue https://www.drupal.org/project/scheduled_updates/issues/3363800 📌 Drupal 10 compatibility Needs review , so maybe let's focus on that issue.

Kevin Hoffmann → made their first commit to this issue’s fork.

Kevin Hoffmann → changed the visibility of the branch 3228974-query-for-retrieving to hidden.

Kevin Hoffmann → changed the visibility of the branch 3228974-query-for-retrieving to active.

I added a fork for version 2.x that sets the access checks to false like @hchonov suggested. This fixes an issue with node related update events - especially unpublished ones.

The problem is that we fetch all nodes with update flags first before deciding who should run the update. Setting the access check during the retrieval to TRUE means cron and drush runs will not be able to see unpublished nodes and therefore miss those completely. An alternative would be to switch to user 1 during query execution but might as well just ignore the access check then for the same result. We cannot switch to a specific user yet during that query as we dont even know if and how many updates there are and which nodes are affected.

Each specific update will then later be executed as the user specified in the modules configuration.