Enable statement store in polkadot-omni-node and polkadot-parachain

[gui1117]

We want to enable statement store for people chain.

This PR introduces and enables the statement store and add a new argument disable_statement_store in polkadot-omni-node-lib.
This takes effect in polkadot-omni-node and polkadot-parachain and any node depending on polkadot-omni-node-lib.

The reasoning is following other service such as offchain_worker the default behavior is to support it, otherwise I expect not many collator to explictly opt-in (but I can be wrong assuming this).
Do system chain collator use omni-node or polkadot-parachain? we could otherwise only enable it for polkadot-parachain. Or we could also create a new binary for people chain and enable it only for this new binary, and remove people chain from polkadot-parachain.

If the runtime doesn't support the API then it any submission will fail with Error calling into the runtime.

It would be ideal to target the next cut-off for this issue/PR given that it can take time for node operator to update their node.

To have a configurable CLI and default behavior for statement-store, I did in this PR: #8421

[gui1117]

/cmd prdoc --audience node_dev --audience node_operator

[gui1117]

This is ready to be looked at

[georgepisaltu]

Looking at the code, I think we could get away with always enabling the statement store (i.e. not having it be an Option in the node spec) since it would just be inaccessible if the runtime API doesn't allow it, but I'm happy to move forward with this.

[serban300]

As per the offline discussion, should we disable the statement store by default ?

[gui1117]

If we disable by default I fear nobody will enable it. But maybe it will be enough with the few that will enable it.

I feel going into a dedicated binary for people chain seems the better then no?

[serban300]

I think that having a dedicated binary for the people chain would create more complications. We would need to release one more binary, change all the tests that involve the rococo-people chain to use the dedicated binary, change the deployment process only for the people chain. I don't know.

Or maybe we should just enable the statement-store by default as it is done here. I'm not sure which solution is the best. I'm curious what others think as well.

cc: @skunert @iulianbarbu @seemantaggarwal

[paritytech-workflow-stopper]

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/14849365823
Failed job name: test-linux-stable