Use FieldValidators on FormFields

[emteknetnz]

Split off from #11403

FieldValidators were added to DBFIelds in the above issue. The following AC was split from it to be done on it's own

Acceptance criteria

• Existing FormField validate methods are updated to use FieldValidator's where possible
• FormField validation docs are updated

New issues created

• Strongly type FormField and subclasses #11462

Kitchen sink CI

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

^ CI failures are existing

CMS 5 PRs

• API Deprecate FormField API #11464
• DOC FormField deprecations developer-docs#627
• API Deprecation notice for FormField::validate() #11472
• DOC FormField::validate() deprecation notice developer-docs#634

Reassign to Steve after merging to merge-up and rebase

CMS 6 PRs

• ENH Use FieldValidators for FormField validation #11449
• API Use updated FormField::validate() signature silverstripe-asset-admin#1508
• API Use updated FormField::validate() signature silverstripe-subsites#608
• API Disable ancestor FieldValidators silverstripe-tagfield#311
• ENH Use FieldValidator for FormFields silverstripe-userforms#1345
• DOC Use FieldValidators for FormFieldValidation developer-docs#621
• API Rename method silverstripe-frameworktest#209
• API Use updated validation API silverstripe-spamprotection#128
• MNT Update unit test silverstripe-admin#1849

[GuySartorelli]

@emteknetnz I took the liberty of removing the link to the campaign admin PR since we're not supporting a CMS 6 compatible version of that module.

[GuySartorelli]

PRs merged