PYIC-6240: Update async CRI audit events

[DanCorderIPV]

DO NOT MERGE before https://github.com/govuk-one-login/event-catalogue/pull/291
Also wait for go-ahead from Analytics and Kiwi

Proposed changes

What changed

Migrate F2F async cri audit events to just async cri events

Why did it change

In preparation for the DCMAW async CRI

Issue tracking

• PYIC-6240

[DanCorderIPV]

How are these changes tested against TxMA to make sure that they correctly match the event catalogue changes?

[blakeyp]

How are these changes tested against TxMA to make sure that they correctly match the event catalogue changes?

In the past TxMA have usually tested the event in staging (or asked us to test and checked the audit logs)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[blakeyp]

Reminder to have checked with F2F (if Data haven't already) as they're listed as a consumer of IPV_F2F_CRI_VC_CONSUMED

[DanCorderIPV]

https://github.com/govuk-one-login/event-catalogue/pull/291 has now been merged, but we should wait until consumers of the F2F events have updated to understand the new events before merging this PR.

[DanCorderIPV]

Conversation with F2F team: https://gds.slack.com/archives/C0440GZHUUX/p1732201961748279

[DanCorderIPV]

Also need to wait for analytics to update their code to accept the new event. Conversation: https://gds.slack.com/archives/C07B1M3FJ67/p1730386568411759