Remove Custom...Server.java classes and replace with Thrift implementation

[Amemeda]

Investigated relevance of a few custom tserver related java classes, deleted them, reworked their implementation with thrift methods

Result:

• Deleted files CustomThreadedSelectorServer.java, CustomBlockingServer.java, ClientInfoProcessorFactory.java
• Added file ThriftServerEventHandler.java
• in TServerUtils.java, implementing method setServerEventHandler(new ThriftServerEventHandler()); to applicable tservers
• removed CUSTOM from ThriftServerType.CUSTOM_HS_HA, updated usages

[Amemeda]

@ctubbsii

[ctubbsii]

I need to check this over again to see if there's anything else, but I did find one thing.

[dlmarion]

I think ThriftServerType.CUSTOM_HS_HA needs to be renamed to remove CUSTOM_ from the enum name and value.

[ctubbsii]

Looks good, but a few thoughts:

1. Still some room to clean up boilerplate to reduce redundant setting of the event handler
2. I am very wary of relying on the ThreadLocal. I think code that uses the clientAddress should really make sure to grab it right after the initial RPC connection, and pass it along, so that way they know they are grabbing it from the same thread in which it is set; I skimmed all the times the thread local was accessed, and it seemed like it was only being done in the same thread where it is set, but it's hard to verify because in many places, we only use it when an exception occurs.
3. Since the enum string was altered, backwards compatibility needs to be fixed if a user explicitly set "custom_hs_ha" in their config instead of relying on the defaults
4. I didn't actually run it to verify that the trace log messages or the audit logs were recording the client address. Please check that and verify that it is still logging correctly.

Of these, 3 and 4 are the most important. 1 and 2 could be done as a follow on. Of those, 1 is the more important one for me, since its smaller and would simplify the utility class a bit, making the code slightly more maintainable (which is important for future work).

[Amemeda]

4. I didn't actually run it to verify that the trace log messages or the audit logs were recording the client address. Please check that and verify that it is still logging correctly.

Here is what I was able to grab for verifying the client address,