Add event type information for event stream in group settings

What does this MR do and why?

This MR resolves the following issues:

• Add a meaningful audit event name for `name` in... (#369320 - closed)
• Add a meaningful audit event name for `path` in... (#369321 - closed)
• Add a meaningful audit event name for `reposito... (#369322 - closed)
• Add a meaningful audit event name for `request_... (#369323 - closed)
• Add a meaningful audit event name for `shared_r... (#369324 - closed)
• Add a meaningful audit event name for `require_... (#369325 - closed)
• Add a meaningful audit event name for `two_fact... (#369326 - closed)
• Add a meaningful audit event name for `project_... (#369327 - closed)

... which are described in this epic and it's parent epic

All these issues were included in this MR because all affect the same two files only.

How to set up and validate locally (via UI)

1. (pre-requisite) Add Group audit events Stream

1. Go to Menu -> Groups -> [Select Group] -> Security & Compliance -> Audit Events
2. Click on Streams tab
3. Add a Stream URL in Group audit events. Tip: https://webhook.site

2. Change settings of the group

1. Go to Menu -> Groups -> [Select Group] -> Settings
2. Change name field.
3. Change path field.
4. Change repository_size_limit field.
5. Change visibility_level field.
6. Change request_access_enabled field.
7. Change membership_lock field.
8. Change lfs_enabled field.`**.
9. Change shared_runners_minutes_limit field.
10. Change require_two_factor_authentication regex field.
11. Change two_factor_grace_period regex field.
12. Change project_creation_level regex field.

3. Wait for the response in your stream/webhook (step 1).

It will look like the following:

{  
  ...
  "entity_type": "Group",  
  "event_type": "group_name_updated"
}

{  
  ...
  "entity_type": "Group",  
  "event_type": "group_path_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_repository_size_limit_updated"
}

{  
  ...
  "entity_type": "Group",  
  "event_type": "group_visibility_level_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_request_access_enabled_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_lfs_enabled_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_membership_lock_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_shared_runners_minutes_limit_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_require_two_factor_authentication_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_two_factor_grace_period_updated"
}

{  
  ...
  "entity_type": "Group",  
  "target_type": "PushRule",
  "event_type": "group_project_creation_level_updated"
}

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.