Add new predefined event tags

What does this MR do and why?

Adds and supports more predefined timeline event tags.

This is in extension to what was already implemented in !100537 (merged) and !102999 (merged)

In this MR, we add new tags that are predefined for usage.

Screenshots or screen recordings

NA

How to set up and validate locally

We can follow the same steps to test mentioned in !100537 (merged) and !102999 (merged) and just use the new tags defined in this MR.

1. Make sure you have Write access to a project.
2. Use any of the new tags introduced here to associate it with a timeline event.
3. Attaching below some examples of creating timeline events and retrieving a timeline event GQL queries for you to test with.

Create a timeline event

mutation CreateTimelineEvent($input: TimelineEventCreateInput!) {
  timelineEventCreate(input: $input) {
    timelineEvent {
      id
      author { id username }
      updatedByUser { id username }
      incident { id title }
      note
      noteHtml
      editable
      promotedFromNote { id body }
      timelineEventTags {
        nodes {
          name
        }
      }
      action
      occurredAt
      createdAt
      updatedAt
    }
    errors
  }
}

Sample input:

{
  "input": {
    "incidentId": "<incident_global_id>",
    "note": "Note",
    "occurredAt": "2022-01-19T12:22:42Z",
    "timelineEventTagNames": [<tag_names separated by comma>]
  }
}

Retrieve single timeline event

query Extract($fullPath: ID!, $incidentId: IssueID!, $id: IncidentManagementTimelineEventID!) {
  project(fullPath: $fullPath) {
    incidentManagementTimelineEvent(incidentId: $incidentId, id: $id) {
      id
      author { id username }
      updatedByUser { id username }
      incident { id title }
      note
      noteHtml
      promotedFromNote { id body }
      timelineEventTags {
        nodes {
          name
        }
      }
      editable
      action
      occurredAt
      createdAt
      updatedAt
    }
  }
}

Sample input:

{
  "fullPath": "flightjs/Flight",
  "incidentId": "gid://gitlab/Issue/496",
  "id": "gid://gitlab/IncidentManagement::TimelineEvent/136"
}

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.