Pushing this out early to catch bot errors since I'm using template tricks
we were not using in HarfBuzz before.

get_glyph_from_name() coming soon.

Such that client cannot accidentally destroy them, even though that
will be a bug in their code...

The get_glyph_from_name() is incorrect; needs fixing.

Turns out we already have support for “post” table, it just needed to be
activated and put in use.

Fixes https://github.com/behdad/harfbuzz/issues/474

Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1452#c5

CC https://github.com/behdad/harfbuzz/issues/139

Yay, works!

Fixes https://github.com/behdad/harfbuzz/pull/377

Should be all good now..

Almost there..

hb_font_get_glyph_extents now works for color bitmap fonts.
Currently only font having index format 1 and image format 17
is supported.

Ouch!

Fixes https://github.com/behdad/harfbuzz/issues/236
Fixes https://bugs.chromium.org/p/chromium/issues/detail?id=627953

To make a release...

Apparently some clients have reference-table callbacks that copy the table.
As such, avoid loading 'glyf' table which is only needed if fallback positioning
happens.

New API:
- hb_font_get_nominal_glyph_func_t
- hb_font_get_variation_glyph_func_t
- hb_font_funcs_set_nominal_glyph_func()
- hb_font_funcs_set_variation_glyph_func()
- hb_font_get_nominal_glyph()
- hb_font_get_variation_glyph()

Deprecated API:
- hb_font_get_glyph_func_t
- hb_font_funcs_set_glyph_func()

Clients that implement their own font-funcs are encouraged to replace
their get_glyph() implementation with a get_nominal_glyph() and
get_variation_glyph() pair.  The variation version can assume that
variation_selector argument is not zero.