feat(protocol): Introduce oracle and system prover concept

[adaki2004]

Modifications:

• Separated Oracle proofs and System proofs (System proofs was the skipped ones, usually called it sometimes "fake proofs", but decided not a good wording.)

Oracle proofs:

• They have to be overwritten (by regular proofs) - otherwise cannot be verified
• They cannot overwrite the existing proof if it's the same
• They can overwrite if FC's data differs

System proofs:

• They are overwriteable and also verifiable as well (UPDATE: was not overwriteable first, we changed)

Related to : #13728

[Brechtpd]

Maybe too late to do this for testnet, but what if we start doing things according to #13693:

• Blocks need a zk proof + a signature (currently just one we generate and share somehow)
• For proofs that need to be skipped only a valid signature is required, the zk proof verification is skipped. Here we force the proof time to be the target proof time to not impact the base fee calculation.

Then, currently optional because not needed, we just have an additional fail safe mechanism to overwrite and lock a fork choice directly, not going through the normal proving code in proveBlock.

EDIT: issue created: #13731

[dantaik]

Lets create an issue for it.

[cyberhorsey]

Will need to add the system prover address of (1) to Taiko client, will create an issue and do it.