Remove Executed Migrations (#7495)

* Polkadot is at .42

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Kusama is on .43

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Westend is at .43

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Rococo is at .42

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Make UMP limits migration more idempotentish

Already 100% idempotent per design, but not it wont try to schedule
an unneeded upgrade. Note that the case that the new upgrade is
already scheduled is not checked. In that case it will still upgrade
the same thing again, but should be no problem.

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Clippy

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Delete old migration code

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* fmt

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Remove old tests

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Polkadot is at .43

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Remove a ton of shit

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Remove more

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Remove unused code

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Rococo is NOT yet at .43, but remove anyway

Rococo is the only runtime that is not yet at .43, but keeping
the migration code just for it is not worth it since devops
can just apply it at any time.

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

* Remove old test

Signed-off-by: Oliver Tale-Yazdi <[email protected]>

---------

Signed-off-by: Oliver Tale-Yazdi <[email protected]>
Co-authored-by: parity-processbot <>