New report for Failed Authentication and menu organization

I have a new report for 'Failed Authentication' similar to 'Failed Webhooks'. Looking at failed authentication attempts across the system is helpful in spotting misconfigured systems that may be tying up authentication workers. I often see this issue when someone changes their credentials but neglects to update stored credentials in their CI/CD systems which in turn causes lots of failed authentication attempts.

The number of reports on HOUSEKEEPING is getting larger. Before I create a PR for my change, should we consider making a submenu under HOUSEKEEPING for Failures and put both 'Failed Webhooks' and my new 'Failed Authentication' under this submenu (for organizational purposes)?

Start by locating the existing “Failed Webhooks” report and the HOUSEKEEPING menu configuration. Compare the proposed Failed Authentication report with the existing report, then determine whether both failures should use a submenu; done means the report and agreed menu organization are implemented and verified consistently.

Written by the indexing model from the issue text.