Apply object display properties when formatting events.

If an object in a formatter tag ({{foo.bar.baz}}) is Displayable,
then we will modify the output based on its display properties.

Currently only supports user links and foreground colours.

This also changes the internal format of nickname links to be
`\u16<nick to link to>\u16<text to show>\u16`, allowing the
link and text to differ. This means if you formatted users
by showing their realname, you could still click them to
open a query.

Closes #424
Closes DMDirc/Plugins#507

Add a display property for linking to users.

Issue #424

Add base interface for objects with display properties.

This will allow the formatter to check if strings coming from
(for example) users in channels should be formatted specially,
such as by colouring or linking them.

Issues #424 and DMDirc/Plugins#507

Copy fat jars into dist/ like normal jars.

I broke it in my interface-extraction shennanigans.

Closes DMDirc/Plugins#509

Add an interface for ColourManager.

Move base command etc to API

Move most events to API

Bulk API move.

Add an interface for tab completers, move to API.

Kill TabCompletionMatches.

Deprecate TabCompletionMatches.

Make it extend a list instead of wrapping it, so we can just replace
all usages with... an actual list.

Extract interface for CommandParser

Add interface for UnreadStatusManager.

Make Command an interface

Rename Command to BaseCommand.

Flip BaseCommand and Command around so everything still works.

Command will eventually become an interface when all usages have been replaced

Move some classes to API

Extract an interface for Styliser.

Remove deprecated styliser methods.

Move static styliser methods to new class.

Minor style fixes

The styliser needs an interface extracting into the API, and
we don't really want huge static methods defined on that.

Use PrivateChat in events, not Query.

Use new config annotations.