Update all references in Cargo.lock for patched crates

[joao-paulo-parity]

Works around https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2115137#L1544

Comparing https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2115137#L1544, which failed to compile polkadot-node-subsystem-test-helpers with errors such as

error[E0053]: method `authority_set_proof` has an incompatible type for trait
    --> /builds/parity/mirrors/substrate/extra_dependencies/polkadot/runtime/rococo/src/lib.rs:1882:31
     |
1882 |         fn authority_set_proof() -> beefy_primitives::mmr::BeefyAuthoritySet<Hash> {
     |                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     |                                     |
     |                                     expected struct `sp_beefy::mmr::BeefyAuthoritySet`, found struct `BeefyAuthoritySet`
     |                                     help: change the output type to match the trait: `sp_beefy::mmr::BeefyAuthoritySet<H256>`
     |
     = note: expected fn pointer `fn() -> sp_beefy::mmr::BeefyAuthoritySet<H256>`
                found fn pointer `fn() -> BeefyAuthoritySet<H256>`

with https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2116743#L1811, which got past that point, I think that the fix is effective.

ref paritytech/substrate#12837 (comment)

[mordamax]

won't it conflict with --locked flag?
#88

[joao-paulo-parity]

No, because cargo check is being executed without the --locked flag below, as intended: Cargo.lock will invariably need to be updated because we're patching packages into projects

[joao-paulo-parity]

I think this bug fix might have uncovered more issues in the integration check. Moving it to Draft in the meantime.

It's working as per https://gitlab.parity.io/parity/mirrors/substrate/builds/2117207 and https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2117249