Migrate Accord Project Stack to Concerto 1.0

[jeromesimeon]

Description

Accord Project has released an alpha version of Concerto. It includes many breaking changes.

This is an umbrella issue to track the work in migrating the Accord Project stack (contract logic DSL, templating system, templates, tools, etc.) to this new version of Concerto.

Tasks

depends on means the dependency has to be completed before the work can really be done on the corresponding project.

• Publish Concerto 1.0.0-alpha (https://github.com/accordproject/concerto/releases/tag/v1.0.0-alpha.6)
• Update Concerto models and publish
• Update Markdown Transform (depends on Concerto models) (https://github.com/accordproject/markdown-transform/releases/tag/v1.0.0-alpha.2)
• Update Ergo (depends on models) (https://github.com/accordproject/ergo/releases/tag/v1.0.0-alpha.4)
• Update Cicero (depends on Ergo) (https://github.com/accordproject/cicero/releases/tag/v1.0.0-alpha.4)
• Update Templates Library (depends on Cicero) (https://github.com/accordproject/concerto/releases/tag/v1.0.0-alpha.6)
• Update VSCode extension (depends on Cicero)
• Update Web Components (depends on Cicero & Concerto)
• Update Documentation

Strategy

First do everything in a systematic concerto-1.0 branch on all repos until we at least reach the template library.

Flags

• This issue isn't about the documentation per se but since it's cross-stack we use this issue to record progress
• This is a very delicate stack-wide change, will require maintainers
• Documentation could happen in parallel, if parallel workers were available.