Major update to 0.9, changes outlined below.

[ANTISPAM SYSTEM]
- Introducing the anti spam system for modules, a means that allows
module authors to prevent their code from being spammed by users or
channels that like to abuse bot powers.
- Four new botrick.conf settings to read up on: enable_antispam,
as_default_timespan, as_default_maxuses, as_default_maxchanuses.
- example.bmd contains an example of the usage of the new anti spam
system.

[OTHER MAJOR FEATURES]
- Fixed a major bug that was causing connection failures in the event
the server was unreachable.
- Implemented a global ignore list feature: Authenticated bot
administrators can now set the bot up to ignore certain users by their
host mask.  These ignores are persistent between bot startups and are
stored in ./etc/ignore.list as a serialized ArrayList.  The new public
BotUtils API calls for working with ignores and host masks are:
isValidHostmask(), isIgnored(), getApplicableIgnoreMask(),
getIgnoreList().
- It is now possible to query the ban list of a particular channel via
BotUtils.isBanned().  You can also manually perform this check yourself
by using BotUtils.getBanList().
- You can now match host masks with wildcards using
BotUtils.wildCardMatch() and BotUtils.isValidHostmask().
- Different versions of the JVM are installed with different setups
supporting different networking settings, and because of this, a JVM
will sometimes be set up to use IPv6 by default.  When connecting to
non-IPv6 hosts, this causes a ConnectException.  For this reason, the
botrick.conf setting “ipstack” now allows you to specify if you will be
connecting to an IPv4 or IPv6 host.
- Speaking of which, botrick.conf is now better documented, so be sure
to check out the new descriptions.
- Modules will no longer have any data passed to them by Java until the
bot is stably connected.
- A ton of Thread.sleep() calls have been eliminated due to the often
irritating necessity of having to catch an InterruptedException with
them.  Thus, BotUtils.sleep() is available for modules and the main
code to use, and does the exception handling itself.
- Logs will now be written out on shutdown if an unexpected shutdown is
initiated.
- Module.java now has access to botrick.conf.
- “this” is a new keyword for the Python module, and is used by some
BotUtils functions to refer to the current module.