OF-2651: Give distinct names to Netty threads
Netty uses various Executor services, that each generate threads. These threads are given a default name, which leads to thread names like: `nioEventLoopGroup-4-1`
This name is not very descriptive. It is helpful, for debugging purposes, to have a name that identifies the source / functionality that relates to the a particular thread.
This commit restores the naming that was used prior to switching to Netty.
OF-2788: (re)introduce threadpool per IO type
Prior to introducing Netty, every connection type (client, component, server) had its own thread pool that was used for processing inbound data.