Optimize LazyDataObject method dispatch

LazyDataObject method dispatch is a bit sub-optimal, as it does not take advantage:

1. Java 8's Method.getArgumentCount()
2. Ability to switch on strings coupled with method names being interned
3. The fact that getters have zero arguments and hence are uniquely identified by their name

Address these issues, hence further improving LazyDataObject hot path.