Subsystems parachains-db data revert

[davxy]

Follow up of paritytech/substrate#11178

When the Substrate backend is reverted some information related to parachains management within the parachains-db should be reverted as well.

We can divide the information added by the blocks after the revert point in two categories:

• data that somehow depends on the blockchain state;
• data that is independent from the blockchain state.

Data that belongs to the first category must be reverted.
If not, it may end up referencing some blockchain data that in the meantime has been wiped out by the overall revert procedure.

Data from the second category is most a "nice to have" cleanup feature.
If this is not reverted it should be a (negligible) leftover that doesn't influence the node's operational status once restarted.

---

Subsystems referencing data within the "parachains-db":

• chain-selection => does need to be reverted (addressed by Chain-selection subsystem data revert #5350)
• approval-voting => does need to be reverted (addressed by Revert approval voting #5438)
• dispute-coordinator => probably doesn't need to be reverted, but there will be some orphaned data until the chain progresses further on the local node.
• availability-store => probably doesn't need to be reverted.