e.g.
 - ability to log ip addresses of respondents
 - configurable bind address
 - reasonably sane defaults (hopefully)
 - survey name as part of output file names

this is just a quick barebones server, which doesn't really do yet what
it is supposed to or what the guile version did.

for now, this is just a simple date picker done via the html input type
"date". Unfortunately, that's not supported by Safari, so the rust util
now prints out a warning if it's used.

I'm not sure if there's any other reasonable option which would go
around this that's not "using a web framework" or "hacking a fallback
date picker which just consists of a couple of combo boxes".

the previous commit introduced handling error messages using a
"setErrormsg" function. This is now also used for the general error
messages which may show up at the bottom of surveys.

However, since js and async things are weird, the code there is still a
long repetitive mess which can't really be cut down further.

In surveys containing radio buttons, there will now be a nice little
hint directly beneath them if none were selected when attempting to
submit (in addition to the relatively nondescript "not all required
questions were filled in"-hint at the bottom of the form)

(it mistakenly set the locale to undefined before)

(from the browser's preferences set via navigator.language and
navigator.languages)

This adds a basic "replace fixed keys"-approach to translating the UI of
surveys. So far this works great, but for complex things it may fail for
some languages — for now I'll just  try to take care not to add any
output that puts things in the middle of sentences, which I think should
work for a simple survey thing.

The default language is still english, which is important as the
language is declared withing a survey config — i.e. if loading it fails,
it cannot be applied, and the "enter passphrase" dialog can also not
change based on locales. This could possibly be fixed by adding an
unencrypted "header" to the encrypted configs, but for now I'm not sure
if that makes a lot of sense — it may be easier to just guess based on
the browser's settings, and otherwise fall back to some specified
default language.

The "thanks for your answers"-page also has no translation so far.