Improve transaction validation in the mempool

[maht0rz]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

• Verify proofs as argument, throw away the tx any proof doesn't verify
• For non-proven appchain deployments, we still need to compile the requires proof, in case it's not a DynamicProof, to be able to validate proofs-as-arguments against that resulting VK. This means that users will have to still produce the proofs that they send to the runtime, but otherwise every use can send unrestricted public input/outputs to the runtime and potentially break the system

[rpanic]

Also, we should sort the returned transactions when returning the from the mempool, so that multiple transactions from the same sender appear in the correct order

[rpanic]

We should also add a configurable maximum block size that the mempool respects