Allow RPC endpoints to use dedicated thread pools

This is a new feature of the RPC framework so that we can isolate RPC message delivery for plugins from normal Spark RPC needs. This minimizes the impact that plugins can have on normal RPC communication - they'll still fight for CPU, but they wouldn't block the dispatcher threads used by existing Spark RPC endpoints.

See parent bug for further details.