Add new_variable_full

Route everything through that.
Add new_variable_enum

This seems to work. Yay.
Whitespace that I don't feel like rebasing

Sigh. Tabs and spaces.
Permit validsettings for string

Also die in new_variable_int and new_variable_bool if validsettings are
given.
Moved log generation code to perl.
Made owl_util_makepath available from perl

There's probably a better way to do this.  Maybe

sub makepath {
        my $filename = shift;
        $filename =~ s{ ^ ~ ( [^/]* ) } { $1 ? (getpwnam($1))[7]
        : ( $ENV{HOME} || $ENV{LOGDIR} || (getpwuid($>))[7] ) }ex;
        return $filename;
}
(http://docstore.mik.ua/orelly/perl/cookbook/ch07_04.htm) or something.

Additionally, I'm not sure why

 PREINIT:
   char *rv = NULL;
 CODE:
 {
   rv = foo();
   RETVAL = rv;
 }
 OUTPUT:
   RETVAL
 CLEANUP:
   g_free(rv);

is the paradigm for functions returning strings, when foo returns `char
*` and not `const char *`.  I've removed the `= NULL` part of the
initlization, which I assume is left over from when we had to NULL-check
things before freeing them, but I've copied the rest of the code.
Moved log file name generation to perl

I don't think that the class/personal distinction is the best for
general protocols, but I don't know what should replace it.  I've made
class-logging default to only zephyr (a slight change from previous
behavior, where jabber MUC's would be logged to $classlogpath, as well
as all non-private non-login messages from other protocols), but made
logging path generation overridable.

XXX Decide whether or not to filter out more 'bad' characters.
Perhaps we should remove '!' because it indicates history in some shells
and makes things obnoxious.
* '~' indicates homedirs in many shells.  I strip it out everywhere
  because I'm lazy and don't want to make a separate regex to strip it
  out only if it's the first character.
* '/' is for separating directories, and we don't want to accidentally
  make subdirectories

We first NFKC for zephyrs, and then apply lc.  The zephyr servers
apply case-folded NFKC (so says
http://zephyr.1ts.org/browser/zephyr/server/zstring.c).  We should
probably use Unicode::CaseFold instead of lc.  I'm also not sure if the
order of case-adjustment and normalization matters.

We first NFKC, then apply lc, to jabbers, as per
http://xmpp.org/internet-drafts/attic/draft-ietf-xmpp-nodeprep-03.html

We now use lc instead of g_utf8_strdown to normalize AIM screennames.
Scrapped the last bits of C code dealing with jabber.

We still have an OWL_PROTOCOL_JABBER in owl.h, but it does no harm being
there, and we don't use any of the other ones except for AIM.  I figure
there's no harm in waiting and ripping all of them out at the same time
in perl/AIM
Moved outgoing zephyr error logging to perl
Moved the checking of whether or not to log messages to perl
Moved notification of message logging to perl
Moved logging-specific variables to perl

But only the ones that could be moved losslessly, i.e., no special
validsettings and not enums.
Moved the last of the logging-related variables to perl

We seem to have picked logpath as the string variable we test in
tester.c.  Since this is no longer in C, I've replaced it with
personalbell (no particular reason for that choice).
Added a logadmin variable for logging admin messages
Ignore kerberos instances in the sender and recipient when logging

This fixes trac-#151 (Handle logging of personal zephyrs from different
instances of Kerberos principals sanely).  Stripping the instance is
only done for the filename, not for the actual log contents.
Log different realms to different files
Make loggingdirection only apply to personals

Fixes trac #242
Display file name on failure to open file
Add IRC logging filename generation

Based on asedeno's comment
"For IRC I'd probably want a combination of network and (channel or
nick)."
Log to subfolders of a base path

A different subfolder for each protocol.