Expand uncaught ValidationException messages

[emteknetnz]

DBField ValidationException started being thrown in #11403

The "message" is usually something simple such as "Must be numeric", which is fine in context of context of validation within forms as their is also a "fieldName" key that can be used to link the message to a UX form field.

However in the case of dev/build or other programmatic tasks, the validation message lacks "fieldName" and "value", which makes debugging harder then it needs to be

Notes

• Value was at one point added to ValidationException the DBField PR - though ultimately taken out. If we proceed with this work it should be added back it

Acceptance criteria

• ValidationException are caught and the "message" is expanded to include the "fieldName" and "value" in dev/build like contexts
• If not already exposed, the classname and possibly record ID for the invalid record are included
• They are not expanded when run in a form submission context e.g. form submission, HTTP request via API

CMS 5

Kitchen sink CI

• https://github.com/creative-commoners/recipe-kitchen-sink/actions/runs/13001456512

PRs

• API Deprecate passing null paramters for Form and ValidationResult methods #11564
• DOC Deprecate passing null paramters for Form and ValidationResult methods developer-docs#678

After merging, reassign to Steve to rebase

CMS 6

Kitchen sink CI

• https://github.com/creative-commoners/recipe-kitchen-sink/actions/runs/13229515256

PRs

• NEW Show more information in ValidationException message #11562
• FIX Pass empty string instead of null for error silverstripe-elemental#1311
• DOC Show more information in ValidationException message developer-docs#677

[GuySartorelli]

PRs merged