fix: remove spec_version check for Centrifuge 1023 migrations

[wischli]

Description

Removes spec_version checks for Anemoy, USDC and EVM Precompile Accountcode migrations.

Apparently, we cannot rely on the result of try-runtime which succeeded for all these migrations. However, in practice neither Dev/Demo nor Catalyst ran the EVM Accountcode migrations (Anemoy & USDC migrations ran on Catalyst in a previous upgrade from 1020 to 1021). My understanding is that at the time of executing on_runtime_upgrade(), the spec_version has been bumped already and LastRuntimeUpgrade updated to the current spec_version. I could not find any way of reading the pre upgrade spec_version.

None of the migrations performs many reads or writes. Moreover, they were adjusted such that no written storage is mutated. Thus, they cannot do harm.

Checklist:

• I have added Rust doc comments to structs, enums, traits and functions
• I have made corresponding changes to the documentation
• I have performed a self-review of my code
• I have added tests that prove my fix is effective or that my feature works

[lemunozm]

Not an expert in this topic, but changes look good!

[lemunozm]

I understand this has not been changed for altair because we are using development as demo now.

[wischli]

The correct reason would be that we had not upgraded Algol or Altair yet. In contrast, Catalyst received two upgrades already from 1020 (current Centrifuge version) to 1022.

[lemunozm]

Thanks for extend!

[cdamian]

Thank you @wischli!