Replication optimization where the network traffic between eureka nodes are considerably reduced by executing the replication events as one batch instead of individual requests.

This has both the effect of reducing the number of threads on the eureka server side and also makes the replication lightning fast (where 100s of replication request are executed at the same time as 1 request). This optimization has a great positive effect of scaling eureka servers much much more horizontally making replication and state maintenance a non-issue when the cluster expands to have more nodes.
Minor changes based on pull request comments.
Separate resource to handle batch requests.
Remove the old way of handing batched requests.
Optimize on EIP binding logic to avoid unnecessary AWS calls per the pull request comments.
Minor refactors and bug fixes.
Merge pull request #68 from karthik-vn/master

Replication optimization where the network traffic between eureka nodes ...