Hot Rod Client RemoteCache#computeAsync() can lose the result of remapping processing when executed concurrently against a new entry

Hot Rod client RemoteCache#computeAsync() API can lose the result of remapping processing when executed concurrently against a new entry.

It appears that this issue can be caused by the missing of specifying Flag.FORCE_RETURN_VALUE to the putIfAbsentAsync() call inside RemoteCache#computeAsync().