Change ExecutionStrategy methods from package-private to protected

[rayokota]

I would like to override/customize the behavior of getAsyncFieldValueInfo in a custom subclass of AsyncExecutionStrategy but cannot easily do it. Since the method getAsyncFieldValueInfo is called in both AsyncExecutionStrategy.execute and ExecutionStrategy.executeObject, I can try to override both those methods in my subclass, but I end up copying in a lot more code than if I could simply override getAsyncFieldValueInfo.

Also, in the future I may want to override createDeferredExecutionSupport but I can omit the change to the signature of this method for now if it makes the PR more acceptable.

Thank you in advance.

[bbakerman]

I would like to override/customize the behavior of getAsyncFieldValueInfo

Can you expand more on what new behavior you would like to introduce.

Can you explain more about how much extra code you need to copy?

The background thinking on ExecutionStrategy is that we should never have made it public API. Why? Because the locking that comes from public API in this special case is not worth the price of being unable to change in order to be efficient.

Some people want to write whole new algorithms on how a query is executed and this can't be done via inheritance. The current ExecutionStrategy code is intimately tied to the breath first execution of fields along with the peer Instrumentation classes that reflect that algorithm. Its hard (damn well near impossible) to make new ones.

[bbakerman]

I am closing this PR because we don't have any insight into why its needed.