Smart Contract Interpreter versionning

[bchamagne]

Description

Introduce smart contract versioning.
The user will be able to choose it's version by setting a @version attribute at the top of her/his code. No @version attributes is equivalent to 0.0.1.
Part of #894

There are 2 versions available:

1. legacy / functional lang (= 0.0.1)
2. imperative lang (= 1.0.0)

I move current language into a version0 folder.
The imperative lang is not implemented in this PR but I prepared the ground in a version1 interpreter.
Some files has been renamed to match their modules names.

TODO

• Unplug the worker from version0 and plug it to the dispatcher (Archethic.Contracts.Interpreter) instead.
• Unplug the contracts from version0 and plug it to the dispatcher instead.
• Should I restrict versions to only those existing?

Examples

@version "1.0.0" 
condition ....
actions ...

@version "0.0.1"
condition ...
actions ...

condition ...
actions ...

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Unit tests ✔️
Legacy smart contract ✔️

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[samuelmanzanera]

Is this PR still relevant regarding #894 ?

[bchamagne]

Is this PR still relevant regarding #894 ?

yes, this is step 1/2 (step 2 is #903).
This one prepared the ground to have 2 different interpreters

[samuelmanzanera]

I wonder about the granularity of the versions.
The last digit might not be useful, as the bug fixes will be patched along the way, and the contract code might not be dependent on the bug fixes.
For the second one, I think the enhancements of the interpreter should be retrocompatible within a major version.
But the one is useful because it informs which major version of the interpreter is used and will simplify the writing of the smart contract code.

[bchamagne]

reminder, once merged we need an upgrade to the playground (see: https://github.com/archethic-foundation/smart-contract-playground/pull/21/files#diff-2e3dab7734e486531bea720f3148534abd3b883ae941d433cdf70078a41b2643)