sp-io update

[chevdor]

This PR applies cargo update sp-io into the polkadot-v0.9.10.

The polkadot-v0.9.10 in Substrate saw some changes so we need to update accordingly.

[chevdor]

@tomusdrw we will likely get in this PR the same CI failures as in #285 (I already see the deny issue). Do you want to handle those differently for this PR?

[adoerr]

@chevdor I'm a bit confused, why the sp-io update is needed at the BEEFY level.

Whenver I updated the BEEFY dep in Polkadot I first do a
cargo update -p beefy-primitves
and then a
cargo update -p sp-io --precise [exact commit needed for Polkadot]

This usaully gives the the minimal set of changes for Cargo.lock. What am I missing here 🤔

[chevdor]

The issue is that:

• beefy depends on Substrate
• diener nicely switched all the deps to the new Substrate branch polkadot-v0.9.10
• in the meantime, the branch evolved but the referenced commits did not

At the Polkadot level, running a cargo update -p sp-io gives me missmatches on some deps compared to cargo update -p beefy-primitives. With this PR, I am trying to align the two.

Do you see any potential issue with this update ?