The old approach of including the same source files into
multiple places is less than pretty.  But moving the code
to libply didn't seem right either, since libply is fairly
generic and could in theory get swapped out with a standard
runtime at some point.

Also, exposing libplybootsplash as an external library will
facilitate creating out of tree splash plugins.

We may want to do another convenience lib for plugin
specific apis, or fold window into libply

There was a sort useless layer of indirection between the
window object and splash plugins.  It ended up with
functions like:

void
on_backspace (ply_splash_plugin_t *plugin)
{
  plugin->interface->on_backspace (plugin);
}

Since the individual plugins are aware of the window object
anyway, they can register their own on_backspace et al handlers
without going through the ply_splash_plugin_t layer.

Just makes things more consistent.

The logic for line editing is a little complicated, so it's
best not to duplicate it across all the plugins.  Now we
manage it all from the window.  The plugins now access the
various editing events via there vtable, but that's an
extra layer of indirection that doesn't matter given that
we pass the window to the plugins anyway.  We should drop
that and just have the plugins register for edit events
directly.

This prevents each handler from having to run mbrlen on
its own.

Now we just pass the loop in directly to show and hide,
which makes its lifecycle more clear.