Bump to use newer version of Substrate

[mnaamani]

Do we need this?

paritytech/substrate#13630

┆Issue is synchronized with this Asana task by Unito

[mnaamani]

The next polkadot substrate release which contains the updated trie-db v0.27.1 is v0.9.42 https://github.com/paritytech/polkadot/releases/tag/v0.9.42

[mnaamani]

After reviewing the changes in releases here: https://forum.polkadot.network/tag/release-analysis

I determined that the best version to update to at this time is 0.9.41 and manually bumping the trie-db to v0.27.1

I was tempted to just go straight to 0.9.43 even (current polkadot network release), however there are some high impact changes to the balances pallet. paritytech/substrate#12951 which we would need to understand better to make sure it doesn't break any of the assumptions we make about joystream's staking mechanism with respect to reserved balances/locks and existential deposits.

So our forked version is at https://github.com/Joystream/substrate/commits/joystream-polkadot-v0.9.41-update
built on-top of https://github.com/paritytech/substrate/tree/polkadot-v0.9.41 - compare the diff Joystream/substrate@polkadot-v0.9.41...Joystream:substrate:joystream-polkadot-v0.9.41-update

This includes a fix for the staking pallet migration which removes a wrong post runtime upgrade migration assertion.

Implemented in #4932