The beginnings of some command line testing code.

It strikes me that app/tests/lib is browser oriented so maybe having
app/tests/command-line is handy for tests which can run using only the
metapolator command line tool.

The fontforge-export-subset.py file is a utility that allows you to
cherry pick one or more glyphs from a font and export the result to a
new UFO file. Handy when you are only interested in a specific subset
of glyphs and don't want to congest the machine by having metapolator
work on glyphs that you are not interested in for the test at hand.

The command-line/interpolate subdirectory contains the start of a test
for non-glif interapolation. I started with test.sh and then moved that
to test.js so that xpath evaluation and other tools are supplied by
npm instead of various third party binaries on the system.

The test.js uses nexpect and xpath to start processes and test various
XML files in resulting UFO files by checking if nodes at specific locations
exist and have an expected content.

interpolate-for-non-glif-investigation.sh remains a shell script, it
is mostly a series of calls to the metapolator command line tool to
perform work.

Comments and suggestions welcome.
I think this is interesting, because when I wrote the first metapolator commands, I was also thinking it is maybe like git. I did not build this into the `init` command, granted, but e.g. the red-pill had to be started from within the project directory.
One of our first bug reports from a user a user was #133