CMS Validators store configuration outside the context of Document Type definitions depending on them and without versioning like them

Changes to CMS (Document field) validators will be immediately effective, thus for for draft as well as published document types. And for all document types using them.

Also, (named) validators like using the RegExCmsValidator are very opaque from their usage POV. It might be much more effective and easier to use if the regex expression to be used could be specified directly/only on a specific Document Type field configuration instead.

This also impacts the new ContentTypeService which currently cannot easily and/or transparently capture the document type validation rules to make them available for other use-cases than only the CMS itself.
This relates to (but is different from) CMS7-7044