Add Travis configuration

We already have a buildbot running on-premise, which builds packages for
a multitude of systems; but since it is behind a firewall, it does not
(and cannot) integrate with github.

Add travis instead, which can't test as much as the buildbot, but will
give us at least a useful basic "it compiles!" test.
Initiate the "about middleware" application for Linux
Check uname and show the output
Split version number up into version number and build id
Use "" rather than <> for includes in the current directory
Show the build date, too
Make URL look good.
Reorder

The bitness is more interesting than the rest of the uname data
Don't forget to end gtk_list_store_set() calls properly
Show distribution-related information

call lsb_release -<something> -s and show the result
Make sure the UI definition is shipped
Unbreak distcheck
Look for and display location of PKCS#11 modules
Use the libdir which was specified to configure rather than guessing
Remove no longer needed file
Ignore generated files
Whoops
Update packaging
Look for, and show, the viewer
Don't show the window until it's fully built.

This might have a slight performance impact, but is mostly useful for
debugging, really.