Standardise casing on ids in WorkflowMessages

[eileenmcnaughton]

bOverview

Standardise casing on ids in WorkflowMessages

Before

As @seamuslee001 noted the id fields on the Workflow messages have a mix of casing - ie contributionId but eventID, participantID, membershipID`

After

They all use consistent casing - ie contributionID

Technical Details

This resolves the inconsistencies in id fields in the workFlowMessages

My general feeling is this hasn't really been adopted outside of core as yet as it has been so immature so I'm fixing the core uses - these are all heavily tested

Comments

I added to the apiv4 changelog - not strictly an apiv4 thing but that is the supported way to call them - worth a release notes callout
https://lab.civicrm.org/documentation/docs/dev/-/blob/master/docs/api/v4/changes.md

[civibot]

(Standard links)

• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).