Refactor DEX to fit tx limits & misc improvements

[mitschabaude]

fixes #847
fixes #848

• add variant of the DEX example which makes use of a 2-step pattern (1. dispatch action - 2. reduce) to implement its methods within the account update limit.
  • supplyLiquidity (this didn't need actions, but some changes to this.token APIs to enable reusing AUs
  • redeemLiquidity
  • swap (same as supplyLiqudity, didn't need actions)
• also uses events in the new example
  • emit some events
• create & successfully run a run-berkeley.ts script which runs through the happy path of setting up all zkApps, supplying & redeeming liquidity, and performing a swap;
  • DEX account (on-chain state = total supply of liquidity token): https://berkeley.minaexplorer.com/wallet/B62qpeQuY8d97Gc9p2CJbnCBs4eeuqgcncLHnj2Spu519y6fzkz5UUw
  • user account which holds 3 different tokens: https://berkeley.minaexplorer.com/wallet/B62qigeb4rz3UJu7Xs4XQY4qdrsWcQg1ouU5rh3a92aDNA2PCxTYqh5/tokens

Various snarkyjs improvements that helped me achieve this DEX refactor:

• fix the way that transaction limits are counted (the protocol counts the fee payer as signed account update, while snarkyjs didn't count it before)
• add state.getAndAssertEquals() and state.fromAppState(), doccomment all state methods
• make token APIs (mint, burn, transfer) accept account updates or smart contracts as sender/receiver (to avoid creating unnecessary account updates)
• add an advanced option to reduce to skip adding the action state precondition (necessary for when we want to reduce actions on a different account than our own and need permissions for doing so)
• add reducer.forEach(actions, ...) which is just reduce(actions, ...) without a state
• Make the { fromActionState, .. } config optional in all versions of getActions
• Make much heavier use of AccountUpdate.label in many methods that create account udpates, to make tx.toPretty() output easier to understand. Also, add a label for the fee payer.
• Fix to the @method wrapper: use cloned method inputs for hashing the function signature for callData, so that the hash is not changed by the method mutating the inputs
• Fix to the @method wrapper: in the composability case, no longer assume that MayUseToken.InheritFromParent is the correct default for the caller method (this was based on an earlier version of mayUseToken plus a misunderstanding about how it was supposed to work)
• Export TokenId directly instead of a never-used Token class which contained the TokenId module as (hard to find) static Token.Id
• add Permissions.allImpossible() for a set of permissions where nothing is allowed (more convenient than Permissions.default() when you want to make most actions impossible)

[mitschabaude]

TODO: still have to update the changelog

[MartinMinkov]

Additional Question: Would it be worth hooking this up to CI and the Voter app? It doesn't have to be in this PR or anything cc @jasongitmail @nicc

LGTM! 🥳

[MartinMinkov]

Calling for the help of @barriebyron here for these doc comments 😄 Would you happen to have any suggestions for the wording of these doc comments? Just for context, these comments will be shown to developers when they inspect the methods and in our API Reference docs.

[barriebyron]

I suggested some text changes, lmk if helpful @MartinMinkov and teach me where feedback is ineffective, ty!