Being conservative.  Also not sure it makes any real difference
in our codebase.

Part of https://github.com/harfbuzz/harfbuzz/issues/1809

This actually makes it build now!

Part https://github.com/harfbuzz/harfbuzz/issues/1809

Keeping open to add tests, CI, etc.

Part of https://github.com/harfbuzz/harfbuzz/issues/1809

Part of https://github.com/harfbuzz/harfbuzz/issues/1809

This was non-standard, and unused anyway.

Part of https://github.com/harfbuzz/harfbuzz/issues/1809

Part of https://github.com/harfbuzz/harfbuzz/issues/1809

Part of https://github.com/harfbuzz/harfbuzz/issues/1809

Part of https://github.com/harfbuzz/harfbuzz/issues/1809

Make harfbuzz working on all existing versions of Windows

I tried to cross compile harfbuzz for Windows and an error was generated because `DWrite_1.h` was not found.
This happened because the filesystem is case sensitive and for this reason that include file was not found.
The right name of the file to be used is `dwrite_1.h`, with all letters not capitalized:
https://docs.microsoft.com/en-us/windows/desktop/api/dwrite_1/
I also verified in the installation of VS2017 with Windows Kit v10 and in that place it was also lower case.
So, in my opinion it should be better to change this.

Not used anymore since DWRITE is loaded dynamically.

Also checks if DWriteCreateFactory() has been executed successfully.

https://github.com/harfbuzz/harfbuzz/pull/1799

[CFF] fix for Subrs null ptr access

It makes sense to disable this code these if editing is not needed.
However, this is also necessary to correctly display emoji sequences
in right-to-left direction.  For that reason, don't auto-disable it.

Part of https://github.com/harfbuzz/harfbuzz/issues/1652

Part of https://github.com/harfbuzz/harfbuzz/issues/1652

Don't know who would want when why.  But makes sense to have.

Part of https://github.com/harfbuzz/harfbuzz/issues/1652