Use new darc-rule only in version 3

[ineiti]

There has been a mismatch with the release of the nodes and the spawning of contracts. To keep the chain in a consistent state, the version needs to be updated to version 3, and only then the new darc rule needs to be used.

---

🙅‍ Friendly checklist:

• 0. Code comments are added (or updated) when/where needed and explain the WHY of the code.
• 1. Design choices, user documentation and any additional doc are added (or updated) in READMEs.
• 2. Any new behaviour is tested and small units of code that can be are unit tested.
• 3. Code comments are added on tests to explain what they do.
• 4. Errors are systematically wrapped with a meaningful message using xerrors.Errorf and the %v verb.
• 5. Hard limit of 80 chars is always respected.
• 6. Changes are backward compatible.
• 7. Indentation level does not exceed 5, although 4 is already suspicious.
• 8. Functions, files, and packages are kept to a manageable size and decomposed into smaller units if needed.
• 9. There are no magic values.

[Gilthoniel]

Why is this in the PR ?

[ineiti]

Because BEVM is now part of the byzcoin-conodes, and there are BEVM instructions in the chain. So if BEVM is not included in bcadmin, the command to verify the chain, bcadmin db replay, fails...