This reorganizes some of the code that will be used for parsing
messages, as well as changing the loading of messages from JSON to use
SwingWorker for loading

Adds proper formatting/highlighting for the 'raw' message view

Fix the parallelization so that it actually works.

There is still future stuff to do (a way to see overall progress of the
save, not just task-based progress would be nice) but it is certainly a
start

This refactors the app to actually use the parallelized DB support.

Unfortunately, it doesn't actually work due to issues with the external
batch support for NamedPreparedStatement.

The next step is that, once NamedPreparedStatement has been reworked to
actually have a working version of the feature, to adapt this to use
that

Part one of the DB updates - switching to using a centralized source
that uses a executor to parallelize.

I'd imagine the performance would be more arse than it already was if I
ran it now, which is why the next step is to change the save action to
use SwingWorker and be parallelized per conversation.

After that, set-up the UI for BatchTaskProgressPanel, and configure
those SwingWorkers to use it