fix: Removes duplicate log events.

[ShadeWyrm]

Fixes #6547

Checks what elements of a template are changed before throwing log events that the element was indeed changed.

Remaining Issues:
Download form (says Form JSON updated, don't include)
API key generation/deletion (does not include actual details, only placeholders)
Manage access (missing strings to make it user-readable, sometimes missing attributes {{userEmail}}

To be fixed in a later itteration:
#6627

[timarney]

Thinking maybe this wasn't caught in the original PR but when I change classification I'm not seeing the changed to value

"cmj8qf3du0001nb0dejo7nx98","tim.arney@cds-snc.ca","""Data classification changed""","2025-12-16T15:34:28.633Z",
"cmj8qf3du0001nb0dejo7nx98","tim.arney@cds-snc.ca","""Data classification changed""","2025-12-16T15:33:51.194Z",
"cmj8qf3du0001nb0dejo7nx98","tim.arney@cds-snc.ca","""Data classification changed""","2025-12-16T15:32:54.874Z",

[timarney]

Will wait for QA but outside of my comment on classification this seems to be working well.

[anikbrazeau]

QA testing

Language

• English
• French

Form

• Create form
• Update form name
• Update form content
• Duplicate form
• Archive form
• Restore form
• Download form
• Publish form

Settings

• Change classification
• Set form purpose
• Turn on/off saving progress
• Open/close form
• Schedule closing date
• Turn on/off notifications

API

• Generate API key
• Re-generate API key
• Delete API key
• Increase throttling

Team members

• Grant access
• Revoke access
• Invite user
• Accept invitation
• Decline invitation
• Cancel invitation

Responses

• Receive new response
• Download response
• Confirm response
• Delete response
• Report a problem with response

Issues

• Update form name (does not include what it changed to)

• Archive form and Restore form (does not have corresponding string, should not have delete, use restore instead of unarchive to match interface language)

• Download form (says Form JSON updated, don't include)

• Publish form (shows draft responses deleted which is perhaps unexpected)

• Form purpose (should be Intended use and have administrative and non-administrative spelled out to match interface language)

• Saving progress (true/false should be ON/OFF to match interface language)

• Notification setting (does not have corresponding string)

• Open/close form (should be more specific, not just about scheduling if not scheduled)

• API key generation/deletion (does not include actual details, only placeholders)

• Manage access (missing strings to make it user-readable, sometimes missing attributes {{userEmail}}

• Responses (events not included?) Add key actions related to responses to form activity spreadsheet clients can download #6627

[github-actions]

🧪 Review environment

https://jnbcxxad2xkjjxc5h4er32b43m0fbano.lambda-url.ca-central-1.on.aws/

[ShadeWyrm]

@anikbrazeau can you retest when you have time?