chore: give best practices around mutations

[cmwylie19]

Description

Provide documentation/education on why it is a best practice to always Validate any Mutations.

Related Issue

Fixes #899

Relates to #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Unit, Journey, E2E Tests, docs, adr added or updated as needed
• Contributor Guide Steps followed

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.52%. Comparing base (7d4df9d) to head (39ca452).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1672   +/-   ##
=======================================
  Coverage   79.52%   79.52%           
=======================================
  Files          48       48           
  Lines        2090     2090           
  Branches      461      452    -9     
=======================================
  Hits         1662     1662           
  Misses        398      398           
  Partials       30       30           

[btlghrants]

I suggested a couple of links & call-outs the one of the config traps that led to us wanting to add this write-up.

Feel free to move it around / re-write those as you will -- just wanted to be sure we had some actionable links / descriptions of how someone might get themselves into trouble by not validating.

[samayer12]

Good PR on mutations. Used this as the basis for a Pepr tip on 16 Jan 2025.

[btlghrants]

Seems right enough to me.