The methods declared in IRCClientSessionDelegate and
IRCClientChannelDelegate now have an additional parameter, for
the session or the channel to send a reference to itself. This is
in order that a single delegate object may manage multiple sessions
or channels, and disambiguate between them when receiving messages.

IRCClient is now entirely text-encoding-agnostic[1]. It takes values
for messages, nicks, channels, etc. as NSData objects which should
contain null-terminated C strings, and returns values likewise.
The 'encoding' property of IRCClientSession and IRCClientChannel is
no longer used for any[1] internal functions. It is the responsibility
of the framework's user to select an appropriate encoding for display
of received C-strings (storing this encoding with session and channel
objects is the function of the 'encoding' property).

[1] The one exception is the reply string to CTCP TIME requests, which
uses the specified encoding for the session.

IRCClient now supports PRIVMSG and NOTICE messages that are not
addressed to the client's nick, nor to any channel the client is on.
An example is the AUTH messages that some servers emit at the start
of the connection process.

In some callbacks, NSData objects to be passed to IRCClientSession's
event handlers would be nil (if e.g. a user parted a channel without
giving a reason). Those object references would then be sent messages.
This is bad. Instead, an NSData object is always allocated now, even
for blank reasons/messages/notices/etc. This object simply contains a
single null byte (i.e. it holds an empty, null-terminated C string).

IRC_Numerics.plist contains a mapping of known IRC numeric message
codes (taken from https://www.alien.net.au/irc/irc2numerics.html) to
their ASCII names. This is mostly for internal dev/debugging use.

Rather than have properties, setting which does nothing, we now
have readonly properties for nickname/username/realname, and a single
setter method, which may be called prior to the session connecting.
That way we won't have people setting the properties, and having the
properties then not reflecting the state of the connection!

Default (blank) topic is now properly null-terminated.

The IRCClientChannel 'name' property was readwrite. This is obviously
incorrect - you cannot change the name of a channel the user has joined,
so you shouldn't be able to change the object's name property!

IRCClient should no longer have any issues with null termination
of strings (expecting terminated strings and not getting them,
or vice versa).

IRCClientChannel and IRCClientSession had properties which were defined
and adorned with memory management keywords in contravention of best
practices and Apple recommendations. These have been rectified.

No API changes accompany this fix.

The comments for some methods in IRCClientSession.h and
IRCClientChannel.h were incorrect (they still talked about the old
event names, from version 1.0). This commit fixes those errors.