Update fail2ban.upstart

It was actually a little problematic :)
Update fail2ban.upstart

No longer directly exec the server, do not remove the PID file because it is unnecessary to do so. No longer respawns because Upstart can not track the process with the starter command.
Block brute-force attempts against the Monit gui
ENH: Move traceback formatter to from tests.utils to helpers

Now allows for tests to be removed from package if desired
TST: Add Python 3.4 for TravisCI
Revert "TST: Add Python 3.4 for TravisCI"

This reverts commit a3f8b943a3d891f7a48debf9b3dfa8902a45b5cb.

TravsCI doesn't support 3.4...yet
Tidy up filter.d/monit.conf, make regex more complete.
Add ChangeLog / THANKS entry.
Add test cases.
Change Upstart job to track PID of the server

This only works correctly if the client does not fork itself when starting the server (which forks twice further).
Update Upstart job: uses stop command in pre-stop, removes PID file in post-stop
DOC: Add notice message for systemd backend when no journal match
Added foreground and background options to fail2ban-client
Updated man page for new options
Added f and b to cmdOpts.

f = start server in foreground; b = start server in background (default).
Merge pull request #703 from kwirk/journal-match-notice

Add notice message for systemd backend when no journal match
BF: bantime < 0 database should return all bans, as they are persistent
Added more specific help message to fail2ban-client with -f option
Even stricter monit regex, now covers entire line
A few final touches on the Upstart job

(a) use static-network-up, since it is more generic than the started networking event
(b) do not hook into network deconfiguration to speed up shutdown
(c) expect fork, per the use of the "-f" option
(d) use a variable for the run directory to make changing it simpler
(e) handle the situation of a left over socket file
(f) use the -f option to be able to track the PID
DOC: minor -- tabify docstring in badips.py action
BF: fail2ban-regex assertion error caused by miscounted "missed" lines

Caused when removing lines as part of multiline regex, which had been
previously considered missed.