Increase or remove the limit on the number of AccountUpdates

[dfstio]

There is a limit on the number of AccountUpdates in the transaction that is defined as

10.26*np + 10.08*n2 + 9.14*n1 < 69.45
    where np: number of single proof updates
    n2: number of pairs of signed/no-auth update
    n1: number of single signed/no-auth update
    and their coefficients representing the cost
  The formula was generated based on benchmarking data conducted on bare
  metal i9 processor with room to include lower spec.
  69.45 was the total time for a combination of updates that was considered
  acceptable.
  The method used to estimate the cost was linear least squares.

https://github.com/MinaProtocol/mina/blob/develop/src/lib/node_config/unconfigurable_constants/node_config_unconfigurable_constants.ml

Current limits significantly constrain zkApp composability. The max number of AccountUpdates with proof authorization is five, and in the case of token accounts, only two (https://discord.com/channels/484437221055922177/1282303057526263879).
For comparison, UniSwap has 16 core contracts and 30 periphery contracts with approx. 200 methods.

Increasing or removing the limit will help create complex zkApp using many contracts that call each other.

Discussion on Discord:
https://discord.com/channels/484437221055922177/1278455824972517396/1279165276880900207
The connected issue on having the caller field in the AccountUpdate:
o1-labs/o1js#1817