smart rollup: Test persistence across Tezos protocol upgrade

We must ensure that a smart rollup does not break when migration happens, relatex manager operation does not fails after a migration.

• add messages :: internal, external, and with tickets in next. !8251 (merged)
• cement in next a commitment published in pred. !8255 (merged)
• recover bonds in next where the commitment was cemented in pred. !8270 (merged)
• refute in next commitments published in pred :: start a game, play a valid move and timeout. !8273 (merged)
• outbox message in next where the commitment was cemented in pred. depends on #2901 (closed)