Fix fetchActions, part 2

[mitschabaude]

• fixes fetchActions returns one action too many #852
  • if fromActionState is used, the archive node returns one block too many (namely, the one that ended in fromActionState). we check for this in snarkyjs and correct if necessary
• refactored fetchActions / getActions functions throughout to improve readability and do less back and forth conversion.
  • don't store action states with base58 tokenId encoding. Instead, store them as decimal strings which is cheaper to convert to and more consistent with other APIs like graphql
  • fixes Change internal types stored for actions data to be Fields rather than strings #795
  • throw an error in LocalBlockchain.getActions when fromActionState or endActionState aren't found; filed issue for archive node to do the same: Archive node silently returns an empty array when given a non-existing fromActionState Archive-Node-API#77
• reverts Fix fetchActions #844 which fixed the order that actions are processed inside reduce, but broke hashing which rely on the reversed order; instead, reverse back inside reduce and otherwise keep the reversed order that is consistent with how actions have to be stored on the account update

[shimkiv]

LGTM, Thank you