Add general authentication audit events to top-level group for Enterprise users
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=525917)
</details>
<!--IssueSummary end-->
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
A group with [Enterprise users](https://docs.gitlab.com/user/enterprise_user/) should be capable of viewing authentication events for their enterprise users. Such as when a login occurred with standard or two-factor authentication or if an authentication failed.
Example events:
- `Signed in with STANDARD authentication`
- `Signed in with TWO-FACTOR authentication`
- `Failed to login with OTP authentication`
- `User access locked`
- `User access locked - excessive failed login attempts`
- `User access locked - sign in from untrusted IP address`
- `User access unlocked`
- `{Provider} login failed`
- `GITHUB login failed`
- `GOOGLE_OAUTH2 login failed`
Slack discussions:
- https://gitlab.slack.com/archives/C079EHT9AMU/p1740698460029069?thread_ts=1740614512.094509&cid=C079EHT9AMU
- https://gitlab.slack.com/archives/CLM1D8QR0/p1740688186827429
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
-->
<!-- Label reminders
Use the following resources to find the appropriate labels:
- Use only one tier label choosing the lowest tier this is intended for
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
issue