Describe the Bug

When adding a CSV-field we currently can't prevent empty fields. Even if we set 'not-null' to true, it's still possible to create empty entries.
This happens for csv (=text) as well as json (=array) fields.

To Reproduce

1. create a field test as csv, do not allow null-values, default-value is automatically set to null
2. Create an entry with a value
3. delete the value & save again
4. --> it's inserted as "empty" instead of null and therewith valid

Even with custom validations it seems not to be possible to prevent empty json / csv.

For json it's somehow related to #7277 but as csv are stored as strings I'd expect it to work

Directus Version

10.12.1

Hosting Strategy

Self-Hosted (Docker Image)

Database

Postgres