Add categorized protocol error view

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
We are currently hosting a big nextcloud with a lot of users, causing a lot of protocol messages:
24580 Fehler in den Protokollen seit 8. April 2024 (24580 errors in protocol since 8. April 2024)
A lot of errors are just the same:

• InsufficientStorage Insufficient space in /some/users/directory, 49303676 required, 48654 available
• Login failed: 'test1' (Remote IP: '10.20.30.40')
• LocalServerException No DNS record found for owncloud.mathematik.tu-dortmund.de error while discovering ocm provider (some app warning I couldn't care less about)
• TooManyRequests Exception thrown: OCA\DAV\Connector\Sabre\Exception\TooManyRequests Exception thrown: OCA\DAV\Connector\Sabre\Exception\TooManyRequests
• some more ....

Describe the solution you'd like
There are just errors/warning flying in at /settings/admin/logging and I would like to have them categorized in the view, there is no point in seeing the same errors over and over again, some bigger mistakes are hidden between them and the current solution is to manually search in the logs. So additionally to the full log view I would like to have them categorized by the main exception, and then, maybe listed in a sub menu (or spoiler style?) list them individually. This way I can see errors that only occurred once without using a dedicated log scanner.

Example:

Describe alternatives you've considered
Alternatively I'd like to ignore/disable some errors:

• if the user exceeds his storage quota I don't need an exception for this
• if somebody is sending too many requests I don't need an exception for this
• If somebody fails his login, I don't need an exception for this

Additional context

Start at the /settings/admin/logging view and trace how protocol entries are displayed. Review the requested grouping examples and determine how repeated errors can be categorized while preserving individual messages and the full log view. Done means administrators can identify one-off errors without manually scanning or using a separate log scanner.