Add endActionState and fromActionState to fetchActions

[MartinMinkov]

Description

🔗 Resolves #802

This PR introduces fromActionState and endActionState parameters to the fetchActions function in SnarkyJS. This enhancement allows us to fetch only the necessary actions to compute the latest actions state, instead of retrieving the entire actions history of a zkApp as done previously.

With these improvements, we no longer need to start from an empty action state and apply hashes to derive the current action state by analyzing each block from the beginning of a zkApp's history. Instead, we can utilize the new actionStateTwo field returned by the Archive Node API. As actionStateTwo represents the second latest action state calculated, it serves as a safe starting point for deriving the most recent action state. We can now apply AccountUpdates to the actionStateTwo value to compute the current action state.

Furthermore, users can now provide a fromActionState parameter to the Archive Node API, which will return actions only after the specified action state. This feature offers a filtering option in SnarkyJS that was previously unavailable.

Please note that this PR relies on o1-labs/Archive-Node-API#71.

[mitschabaude]

Mostly looks good, although I would change the 'actionHash' terminology to 'actionState', and make sure the local and remote Mina interfaces are consistent.

A general comment is that we don't have good test coverage for getActions. Ideally, there'd be a unit test which confirms expected behavior on LocalBlockchain (for cases like multiple actions in an account update / in a block / computing action states from multiple blocks with actions). Plus a manual test which confirms it with an archive node, for the time being where the Berkeley test doesn't work in CI