Non-bugfix about zero & wide definition conflicts (again!)

[jquast]

In this update to update-tables.py, 04d6d90ca4a7c3aef1a5a156b277ac9da79abb3a I wrote,

verify-table-integrity.py exercises a "bug" of duplicated tables that has no effect, because wcswidth() first checks for zero-width, and that is preferred in cases of conflict. This PR also resolves that error of duplication.

In that change I used method set.discard() in error, the discard method takes a single item as an argument, while I was providing using a whole set and so it had no effect. Instead, I now use set.difference() to re-assign the set value.

Also,

• the category_codes argument has been removed in update-tables.py, it is not used.
• verify-table-integrity.py has been improved to show both range values in conflict
• verify-table-integrity.py now included as a unit test for a single version of python (3.12)
• new unit test about conflicting wide & zero values. This demonstrates that the update to table_wide.py has no effect, as these tests succeed before and after change to table_wide.py.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0ba0278) 100.00% compared to head (594fc27) 100.00%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #110 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 5 5 Lines 105 105 Branches 25 25 ========================================= Hits 105 105 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.