Update to polkadot v0.9.41

[mnaamani]

Fixes #4918

• update to use joystream substrate fork of polkadot-v0.9.41 branch + related fixes
• Re-enable renaming pallet BagsList to VoterList to be inline with polkadot (to ensure polkadot-js apps staking app compatibility) after modifying the migration in substrate to skip "problematic" post upgrade check.
• bump wasmtime crate to v6.0.2
• bump trie-db to v0.27.1

┆Issue is synchronized with this Asana task by Unito

[mnaamani]

ref: #4736 (comment)

• The bump to wastime 6.0.2 is a security fix. It was part of the v0.9.43 polkadot release. I recommend we keep it. Bump wasmtime from 6.0.1 to 6.0.2 paritytech/polkadot#7144
• Asked about move_pallet / post upgrade assertion on substarte stackexchange

[ignazio-bovo]

LGTM, I have no major remarks
The question on the stackexchange is still unanswered.
If the failing check is suggesting that the keys starting with old_prefix are not exactly removed from storage, does it imply that move_pallet actually performs a copy?

[mnaamani]

If the failing check is suggesting that the keys starting with old_prefix are not exactly removed from storage, does it imply that move_pallet actually performs a copy?

No, I'm pretty sure it does move based on looking at the implementation and testing the chain to confirm nothing was at the prefix anymore.