Make the ordering of accounts in the result of a zkApp txn application explicit

[tizoc]

Explain your changes:

The current version implicitly depends on the ordering provided by the Hashtbl implementation in the base library, which is not explicit. This order my change either by changes to the Hashtbl implementation, or because of changes to this function, so it is important to make the ordering explicit and stable.

IMPORTANT this change introduces an incompatibility with the current berkeleynet, because the order of these accounts in the result will change, affecting the hashing of the scan state.

Explain how you tested your changes:

Not tested yet

Checklist:

• Dependency versions are unchanged
  • Notify Velocity team if dependencies must change in CI
• Modified the current draft of release notes with details on what is completed or incomplete within this project
• Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• All tests pass (CI will check this if you didn't)
• Serialized types are in stable-versioned modules
• Does this close issues? List them

• Closes Fix non-determinism in scan state representation #13433

[tizoc]

!ci-build-me

[deepthiskumar]

!approved-for-mainnet