The checksyle plugin was added to the pulsar sql module to enforce the defined style. All violations were fixed:

- Ordering of imports.
- Formatting of the code.
- Absent Javadoc comments.
- Other small issues.
(cherry picked from commit f6fee1c6)

(cherry picked from commit f88ea9df)

### Motivation

1. Currently, the presto pulsar connector will read synchronously from bookkeeper when it has run out of entries go process.  Basically, we process a batch of entries and then we read more.  Ideally should be doing reading and processing in parallel to increase throughput.

2. Each split initializes their own ManagedLedgerFactory/Bookkeeper client.  We really just need one bookkeeper client to be shared among threads.

### Modifications
1. Rewrote the logic in the Presto Pulsar connector to read async and process in parallel

2. Cache ManagedLedgerFactory to be used across splits

### Result

I see about 2X throughput improvement on single node as well as cluster (2 brokers, 3 bookies, 4 presto workers including coordinator) on AWS

* adding module for Pulsar SQL

* renaming presto pulsar package

* fixing pom and configs

* fixing pom

* using project version variable in pom

* adding comments