[Companion] BEEFY crates renaming

[davxy]

Companion for paritytech/substrate#13484

[acatangiu]

You shouldn't change Cargo.tomls (other than renaming the beefy crates) - aka it should still point to git = "https://github.com/paritytech/substrate", branch = "master"

The companion system will do the rest of the magic:

1. it will cargo patch substrate to the right PR branch for the CI
2. once the PR is merged, it will update substrate references here to the right commit hash in paritytech/substrate/master

[davxy]

@acatangiu I know. Indeed is marked as DO NOT MERGE.

This is a trick to allow to have a successful pipeline when you rename some crates already in the lock file of polkadot.
Without this trick you can't patch polkadot using Diener in the Substrate job.

This will be reverted just before merge (I already used this trick for GRANDPA crates renaming in a prev PR)

In short the steps that I've used is:

1. let polkadot companion point to your patched branch directly
2. let the substrate polkadot companion job pass
3. merge substrate PR to master
4. revert polkadot companion to point to paritytech
5. merge polkadot

AFAIK this currently is the only way to do this since diener doesn't support this (yet)

as intended, temporary version

[acatangiu]

Suggested change

	beefy-primitives = { package = "sp-consensus-beefy", git = "https://github.com/paritytech/substrate", branch = "master" }
	sp-consensus-beefy = { package = "sp-consensus-beefy", git = "https://github.com/paritytech/substrate", branch = "master" }

[davxy]

Yeah. you are absolutely right! And I really would :-)
But then if I follow my instinct I have to rename all this stuff as well:

• beefy-primitives -> sp-consensus-beefy
• grandpa-primitives -> sp-consensus-grandpa
• beefy -> sc-consensus-beefy
• grandpa -> sc-consensus-grandpa
• babe -> sc-consensus-babe
  (for the coherence reason 😃)

So probably I would merge this first, just to let polkadot to compile with current substrate master.
Then I can do that in a follow up PR