Fix tier info in audit_event_types script and its output

What does this MR do?

Updates tooling/audit_events/docs/templates/audit_event_types.md.erb to use the new tier badging rolled out today in gitlab-docs#1751 (closed). Also includes the results of running bundle exec rake gitlab:audit_event_types:compile_docs to regenerate the output in doc/administration/audit_event_streaming/audit_event_types.md.

Related issues

Related to Change how we do tier badges (gitlab-docs#1751 - closed)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

doc/administration/audit_event_streaming/audit_event_types.md

@@ -14,7 +14,11 @@ info: "To determine the technical writer assigned to the Stage/Group associated
   edit `tooling/audit_events/docs/templates/audit_event_types.md.erb`.
 --->
 
-# Audit event types **(PREMIUM ALL)**
+# Audit event types
+
+DETAILS:
+**Tier:** Premium, Ultimate
+**Offering:** SaaS, self-managed
 
 Audit event types are used to [filter streamed audit events](index.md#update-event-filters).