No access information is shown when there is no `PageAccesses` objects for the page in the selected interval

[MizukiTemma]

Describe the Bug

Sometimes no information about accesses is shown for some pages. This is confusing for users, not knowing if it is an error, or indeed some kind of result.

Steps to Reproduce

1. Activate Statistics for Augsburg (local environment)
2. Chose an interval (for example last one month, as default)
3. Create some PageAccesses objects for some (not all) pages within the interval you chose
4. Go to the stistics, select all languages
5. See "x Zugriffe insgesamt" for the pages for which you created PageAccesses, see empty row for the pages without PageAccesses objects

Expected Behavior

1. Consider no PageAccesses as 0 access, show "keine Zugriffe"
2. Explain there is no access history data for the page See this discussion

Option 1 is simple but does not cover the case when there is a gap in the access history (example: from some reason the access number for the page xyz on the day dd.mm.yyyy was not collected). BUT: the current implementation does not care whether the history is seamless anyway as long as there is at least one PageAccesses in the selected interval.

Option 2 reports potentiall errors and gaps in the access history but is of more effort and probably cases questions to users.

I'm for option 1, personally.

Actual Behavior

Nothing is shown.

Screenshot

In this case, no PageAccesses object of the selected interval exists for the pages "Über die App Integreat Augsburg", Kontakt zu App Team Augsburg"). There are PageAccesses objects with 0 access for the pages "Wilkommen, "Behörden und Beratung".

Additional Information

Traceback

Related Issues

Blocked by: #4025

Summary of discussion and updates to the description

[hannaseithe]

Before starting this issue I want to wait for the merge of #4060

[jarlhengstmengel]

#4060 is merged now. There is a quite high possibility this Issue is also resolved by #4060, since the probably underlying problem (not all page tree nodes get iterated over) was resolved sonce #4060 introduces the iteration over the shown page tree nodes instead of only the ones whose ids are in the returned data. This is should be testable when #4060 is on the test system.