feat: proposal pre-processing and stamping

[cusma]

Proposals currently look up the Registry configurations for almost all the parameters, depending on their "funding size" (e.g., quorums, durations, etc.). This is why we prevent Registry reconfiguration with pending proposals.

A more efficient and flexible approach would be to "pre-process" the Proposal upon creation, defining its size and stamping all the necessary parameters on its global state at creation time. This will lift the current limitation on Registry reconfiguration with pending proposals.

[tasosbit]

stamping all the necessary parameters on its global state

Just a thought, but given that there is a decent number of values to copy, we could look into storing a struct in a byte-type global state