Add 'warning' and 'critical' alarm priority

Part of #331.
Add 'warning' and 'critical' alarm priority to CLI

Part of #331.
Add 'warning' and 'critical' alarm priority to web

Part of #331.
Update backend doc for new alarm priorities.

Fixes #331.
Add DB schema version info

Part of #122.
Change nipap.conf defaults

Moved nipap.conf to nipap.conf.dist. We will let Debians postinst script
generate the configuration instead or have the user copy the file and
manually edit it.

Part of #122.
Don't ship clean.plsql

It just doesn't make sense..
Add debian configuration scripts

This will have debconf ask the user questions to configure / setup
nipapd. At this point, two actions are supported;
 * if nipapd should be started upon system startup
 * Automatically configuring postgresql for NIPAP

In the future the idea is that this script will help with upgrading the
database structure and similar things as well.

Everything to keep installation as smooth as possible.

Part of #122.
Ignore clean.plsql
Set correct DB version

Part of #122.
Back out incorrect change
Improve nipapd.postinst logic somewhat

Part of #122.
Add debconf to dependencies of nipapd

debconf is not part of Debian essentials so we need to make sure it's
installed before nipapd can be properly installed.

Part of #122.
Fix dist config file

We got these funny log messages from nipapd:
2013-05-10 16:39:29,793: INFO     Listening to address 127.0.0.1
; 127.0.0.1. Use 0.0.0.0 to listen on all
; addresses (change requires restart) on port 1337

The configparser lib parses lines starting with a whitespace as a
multi-line value to the previous key. In the default config file there
was a multi-line comment, but configparser though it was a value.

Default config file has been updated to avoid this.

Fixes #346.
Fix build errors

Default shipping file was recently renamed..
Remove rendered man pages on clean
Fetch search results until screen is filled

The WWW UI has been modified to fetch search results, in the same way as
when a user scrolls down, until either the screen is filled with search
results or we reached the end.

Part of #264
Do auto-escaping in Jinja to prevent XSS

As far as I understand auto-escaping does not have any negative effects
other than slowing down Jinja2 a bit, so I haven't tested much other
than confirmed XSS no longer works.

Fixes #348.
Load ip4r and set owner in debian postinst

This changes the nipapd.postinst script to also load ip4r into the new
database and set ownership on all tables, sequences and views to
'nipap'.

Fixes #122.
Print which db that nipap-passwd operated on.
Fixes #350