As it may cause a race unrelated to the issue actually happened

Using a hack...

What were you thinking? ;)

Needed to make ubsan work.

Fixes https://github.com/harfbuzz/harfbuzz/issues/1174

Decode the string as Python 3 returns bytes string, and also don’t
assume that it ends with a new line.

See also https://github.com/harfbuzz/harfbuzz/pull/1169

See also https://github.com/harfbuzz/harfbuzz/pull/1169

See also https://github.com/harfbuzz/harfbuzz/pull/1169

See also https://github.com/harfbuzz/harfbuzz/pull/1169

I have no way to authoritatively know, but looks like test font only has one
face.  So, adjust test expectation instead.

We might reintroduce it later, but for now remove, as it was unused.
Some things that should have been in this object (drop_hints, etc)
are already in hb_subset_input_t.  So, for now, keep everything there.

Used to be ascent+descent.  Whatever. This is more convenient for
upcoming changes.

New API:
+hb_face_collect_unicodes
+hb_face_collect_variation_selectors
+hb_face_collect_variation_unicodes

Sorry for the noise, downstream custom builders.  Please adjust.

When collecting all codepoints in the cmap avoid using large amount of memory for fonts that declare coverage over all 32 bit integers.

Add the fuzzer test case for feature collection timeout.