[berkeley] Use Proof_cache for Test_zkapp_update tests

[mrmr1993]

This PR builds upon #14030, using the proof cache introduced there to skip the proof generation step on the kimchi side.

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

[mrmr1993]

!ci-build-me

[psteckler]

Would it help to put the proof caches in separate files, so they don't clutter the tests?

[nholland94]

Inlining the proofs into the test files makes them hard to work with. I would really like to see these proofs in separate files that we load inside of the tests. In fact, with the way git works, it would be best to have those files contain compact JSON rather than pretty printed JSON so that every change to those files doesn't incur storing a diff of 60k+ lines of code. We may even want to mark such proof files for storage in LFS, which we can do by giving these files a custom extension (like .proof) and configuring the .gitattributes accordingly.

[nholland94]

Inlining the proofs into the test files makes them hard to work with. I would really like to see these proofs in separate files that we load inside of the tests. In fact, with the way git works, it would be best to have those files contain compact JSON rather than pretty printed JSON so that every change to those files doesn't incur storing a diff of 60k+ lines of code. We may even want to mark such proof files for storage in LFS, which we can do by giving these files a custom extension (like .proof) and configuring the .gitattributes accordingly.

[mrmr1993]

We may even want to mark such proof files for storage in LFS

Didn't we stop using LFS because the repo hit the quota and broke things?

I would really like to see these proofs in separate files that we load inside of the tests.

Will do 👍

[mrmr1993]

!ci-build-me

[mrmr1993]

!ci-build-me

[mrmr1993]

!ci-build-me

[mrmr1993]

!ci-build-me

[rbonichon]

Nice work. Thanks for the changes!

[mrmr1993]

!approved-for-mainnet