Reducing Rollup operation and rollup operation results redundancy

As of now, there are a lot of redundant information in the rollup operations and their results. For instance, in a commitment, each rollup operation batch is associated with a couple of hash (before, after the hash). Similarly, there are information repeated in the operation results that are already present in the operation itself.

Tackling this issue would reduce the pressure of a rollup on the main chain in terms of storage.