Pivoted this to provide new API for updating grant IDs rather than hooks

In T348343#9260290, @Daimona wrote:

In T348343#9259728, @sbassett wrote:

In T348343#9255927, @Daimona wrote:

At any rate, it doesn't really make much difference, except for the (small?) overhead of tracking an additional security patch applied in production. I just thought this could've gone through a simpler process.

Sure. It's completely fine to make this task public now if that's what you and/or other CampaignEvents developers would like to do. And then send a change set up to gerrit for master and any other relevant branches.

I think it should be fairly safe to do so, but would like to hear from @cmelo @MHorsey-WMF @VPuffetMichel.

Surely after aggregation that number should be frozen, a snapshot in time of the aggregated data?

Agreed in Design meeting 18/10/2023 - remove reference to Wikimedia but retain the rest of the message.

@ifried The message here is Wikimedia specific "In accordance with the Wikimedia foundation's terms of use", we will need a generic version.
@gonyeahialam The text is inconsistent with regular styling, the light grey is usually reserved for disabled text or help text. can we agree that it will not be grey and instead the standard black?

@gonyeahialam The AC says that this will appear when enabling registration, but does not specify if it should appear when EDITING registration. If the organiser does not accept the agreement initially, should it show on the edit form for them?

@gonyeahialam Closing this as we think it is complete (in backlog refinement), please let me know if this is a mistake!