different verification keys in different compilation environments

[Trivo25]

Description

Karol reported that the same zkProgram produces different verification keys if compiled on his Mac and on a server. This is fixed by specifying a custom cache location every time

How to reproduce

Need to investigate

[mitschabaude]

if it was fixed by changing the cache directory, what actually happened was probably that it was fixed by recompiling all the keys.
so maybe the cache was stale because the keys changed between o1js versions