Fix for stale gdpo used in UpdateNodeData processing

This MR changes the way we're fetching GDPO in UpdateNodeData command. Previously it was fetched always in a separate call from all the other data (batch request). Now gdpo is fetched in the same API batch request so it is not possible to have a mismatch when first call was for block N and the second batch request call was for block N+1

Description:

This issue was observed with clive list balances command when it failed with:

WaxOperationFailedError: 10 assert_exception: Assert Exception now >= last_update_time: {} manabar.hpp:46 regenerate_mana

because we were taking the now from gdpo which was received in another (previous) api call so it might be fetched for previous block.