Added audit events for update and destroy destinations

What does this MR do and why?

Adding audit events for updation and deletion of instance level external audit event destinations.

How to set up and validate locally

1. Login as instance administrator on gitlab instance, http://gitlab.localdev:3000 .
2. Open http://gitlab.localdev:3000/admin/audit_logs?tab=log in one browser tab.
3. Open http://gitlab.localdev:3000/admin/audit_logs?tab=streams in another browser tab and add a new streaming destination.
4. Open http://gitlab.localdev:3000/-/graphql-explorer for running graphql queries as update is not available on UI currently.
5. Run following query in graphql explorer for listing down all the destinations and note down the gid of the destination you want to update:

query {
  instanceExternalAuditEventDestinations {
    nodes {
      id
      destinationUrl
      verificationToken      
      headers {
        nodes {
          id
          key
          value
        }
      }
    }
  }
}

6. Run following mutation to update the destination, replace the gid with one obtained in step 5

mutation {
  instanceExternalAuditEventDestinationUpdate(input: { 
    id: "gid://gitlab/AuditEvents::InstanceExternalAuditEventDestination/<id>",
    destinationUrl: "https://www.newexample.com"
  }) {
    errors
    instanceExternalAuditEventDestination {
      destinationUrl
      id
      verificationToken
    }
  }
}

7. In http://gitlab.localdev:3000/admin/audit_logs?tab=log, there will be a new audit event related to this update. Please note you might need to refresh the page once.
8. Now visit http://gitlab.localdev:3000/admin/audit_logs?tab=streams and delete the destination.
9. In http://gitlab.localdev:3000/admin/audit_logs?tab=log, there will be a new audit event related to destination being deleted. Please note you might need to refresh the page once.

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.

Related to #404730 (closed)

changed milestone to %16.2

added Category:Audit Events GitLab Ultimate backend devopsgovern documentation groupcompliance missed:15.11 missed:16.0 missed:16.1 priority2 sectionsec self-managed typefeature workflowin review labels

assigned to @hraghuvanshi

marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

	3 Warnings
	b1d116af: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	53b0e0cb: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	Please add a merge request subtype to this merge request.

	1 Message
	CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog. If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Siddharth Dungarwal (@sdungarwal) (UTC+5.5, same timezone as @hraghuvanshi)	Kerri Miller (@kerrizor) (UTC-7, 12.5 hours behind @hraghuvanshi)
groupcompliance	Reviewer review is optional for groupcompliance	Jay Montal (@jmontal) (UTC-6, 11.5 hours behind @hraghuvanshi)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for f3cf477e

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Govern      | 21     | 0      | 0       | 18    | 21    | ❗     |
| Plan        | 47     | 0      | 0       | 41    | 47    | ❗     |
| Create      | 19     | 0      | 0       | 18    | 19    | ❗     |
| Manage      | 12     | 0      | 1       | 12    | 13    | ❗     |
| Data Stores | 20     | 0      | 0       | 15    | 20    | ❗     |
| Verify      | 8      | 0      | 0       | 8     | 8     | ❗     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 127    | 0      | 1       | 112   | 128   | ❗     |
+-------------+--------+--------+---------+-------+-------+--------+

marked this merge request as ready

changed the description

changed the description

changed title from Added audit events for update destroy destinations to Added audit events for update and destroy destinations

@aakriti.gupta Can you please do initial backend review here?

requested review from @aakriti.gupta

@jmontal Can you please do groupcompliance review here?

requested review from @jmontal

I have left a few suggestions, please assign back to me when addressed.

cc: @splattael