Remove Lookup::subset().

Add subset() call for GSUBGPOS struct and its dependencies.
Not hooked up anywhere.

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

Also remove "    " null data for Tag.  Just use zeroes.

This reverts commit 0c1b287b.

This is much faster then calling a bunch of individual add()'s.

Indic shaper uses many stages.  Now we are provably not limiting
functionality whereas the previous limit of 8 was assuming real-world
practices.

Prevents O(n^2) run times.

This new API returns cvXX and ssXX related NameId, things like
featUiLabelNameId, featUiTooltipTextNameId, sampleTextNameId, ... of cvXX
and UINameId of ssXX, in a unified way.

However HarfBuzz currently doesn't expose an API for retrieving the actual
information associated with NameId from the `name` table and that should be
done separately.

In particular, if CoverageFormat2 has unsorted ranges, bail out.
Otherwise, 64k ranges of each 64k glyphs can DoS closure() method.

We can do the same for CoverageFormat1, but that one does not expose
the quadratic behavior, so, fine.

Seems like I messed up; buffer overrun got reported.

Trying to see how many can converted meaningfully.

Such a headache that Windows defines UINT8, ...; Just prefix it.

Ouch!  Missing coords should still be evaluated as coord=0, which
most of the time results in a factor of 0.  We were skipping these,
which was equivalent to a factor of 1.

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

Specificaly, when a range or sorted array has unexpected order, we take that as
font data being garbage and bail out.  This fixes significant slowdown on a bad
version of Chandas font which has a 600KB GPOS with garbage inside.

Later on, I like to add a maximum-work counter for collect_glyphs to protect
against malicious fonts as well.

Fixes https://bugs.chromium.org/p/chromium/issues/detail?id=794896

The three "XXXXX"'s should be switched to false.  Doing that separately for ease
of bisecting...

Not optimized to use sortedness yet.  Also start putting in place infra
to faster reject bad data.

A version of Chandas.ttf found on some Chrome bots has 660kb of GPOS,
mostly junk.  That is causing 48 million of set->add() calls in
collect_glyphs(), which is insane.

In the upcoming commits, I'll be speeding that up by optimizing
add_sorted_array(), while also reducing work by rejecting out-of-sort
arrays quickly and propagate the rejection.

Part of https://bugs.chromium.org/p/chromium/issues/detail?id=794896

To be used to optimize adding a whole bunch of (sorted) items at the same time,
as in CoverageFormat1.

Part of fixing https://github.com/behdad/harfbuzz/pull/605