Feature: Add f_utf_is_print_not() and fix f_utf_is_zero_width().

Feature: Add f_utf_is_print_not() and fix f_utf_is_zero_width().

It turns out that I am mis-using zero-width terminology.
The existing `f_utf_is_zero_width()` actually operates as a "no print" rather than a zero-width.

Solve this by renaming the `f_utf_is_zero_width()` to `f_utf_is_print_not()`.
Then provide a proper `f_utf_is_zero_width()` that operates how zero-width is supposed to be.
This brings the code into compliance.

Add additional types of checks to properly check the leading combining/placeholder.
Once again the editors arbitrarily added spaces in from of combining and joiners despite when I want to literally add a combining and joiner without a space.
Use `sed` and `utf8` to fix the editor caused problem:

```sh
sed -i -e "s|^ ́|$(utf8 -cB U+0301)|g" objects/*-combining_read.txt strings/*-combining_read.txt
```

Update the **Byte Dump** program to use `f_utf_is_print_not()`.