enhancement: account state unit tests

[bleepbloopsify]

testing to see that we do support 32 account state fields, and reject anything above

closes #2669

[bleepbloopsify]

o1js-small [develop-3.0] ♞  ./run src/lib/mina/v1/account-update-state.unit-test.ts
running /Users/leon/github/o1js-small/dist/node/lib/mina/v1/account-update-state.unit-test.js
▶ app state updates
  ✔ should succeed with spec: (fields: 1) (750.01975ms)
  ✔ should succeed with spec: (fields: 8) (430.418625ms)
  ✔ should succeed with spec: (fields: 32) (445.382541ms)
  ✔ should reject with spec: (fields: 33) (326.388041ms)
✔ app state updates (1952.968542ms)
ℹ tests 4
ℹ suites 1
ℹ pass 4
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 2491.93075

Looks like this

[Trivo25]

while this checks if we can declare n state fields, it doesn't check that we actually properly allocate them becuse they are 0 by default anyway. we can do this in a different test but we should make sure that when we declare n state fields, we should also try to modify them

[Shigoto-dev19]

I agree! you can also define a field array Provable.Array(Field, 32) and play around with the number of fields and state changes etc..

[Shigoto-dev19]

Why does the title mention account-update as well?

[Shigoto-dev19]

I agree! you can also define a field array Provable.Array(Field, 32) and play around with the number of fields and state changes etc..