Use Lato on MacOS and Windows

[baconpaul]

As described in #214, we want to use the OFL-licensed font
Lato for all components in Surge with the constraint that we
want to ship the font with the DLL and not require it to be installed
on an end users system.

To do this cross platforms, introduce a new C++ file
"RuntimeFont.h" which defines Surge::GUI::initializeRuntimeFontFromDistribution
and implement that in src/mac/RuntimeFontMac.cpp, Windows, etc.
This PR implements for Mac and Win and neither implements
nor references the symbol in Linux.

This change implements that in macOS by doing the following

1: Introducing the font to resources/fonts
2: Moving the fonts to the bundle with scripts/macOS/package*
3: Moving the font initiation for minifont and patchfont to
runtime rather than surge dll load time (but only do this
for fonts which USE_RUNTIME_LOADED_FONTS, which right now
is only MAC. Once all platforms are done, that switch will
disappear)
4: Write the MacOS specific CoreText code to load a font from
memory into the system

This change implements that in Windows by doing the following

1: Including the font in the .rc file and subsequent res bundle
as a binary
2: Load the font and place it in a well known temp file
3: Load that temp file into the font registry using AddFontResource
4: Following the subsequent standard cfont implementation.

[baconpaul]

@jsakkine a review greatly appreciated

@itsmedavep or @esaruoho if you want to build and test this too that would be lovely

No rush. Nothing here should conflict with anything.

Oh and: Linux was too hard. I gave up. vstgui makes the API too far away.

[jarkkojs]

Should be done in premake5.lua, not here. Is use the standard for us for feature flags?

[baconpaul]

This is the way we staged zoom also. Have a HOST_SUPPORTS_ZOOM (I could do HOST_SUPPORTS_RUNTIME_FONT) and put it in the code; when we got the last host, remove the #ifdef from the code. I could move it to premake but that seems both more icky and less clear to the reader of the code. Mind if I leave it? (Happy to change the name of the variable. USES_RUNTIME_FONTS? HAS_RUNTIME_FONT_SUPPORT? What do you think?)

[jarkkojs]

OK, I'm ready with my review.

[baconpaul]

Thank you. My guess is I will look at this tomorrow maybe Wednesday.

Sorry for using the idiomatic language “plumb through”! Kinda means attach from one end to another like when you are running pipes through a house. I’ll clean it all up.

Appreciated!

[baconpaul]

HI @jsakkine

I rewrote the comments based on your feedback and renamed the function

I didn't change the feature guard - that's the same pattern we used in zoom and I'd sooner stick with it. And I am happy to rename those weirdly named global variables but would sooner that was not intermixed with this function change. Once this is approved I can make that mechanical change, test the builds, and the push it at the same time I push this, but with a separate commit and PR.

Please let me know what you think. Thanks!