Release v0.2.0

[vitsalis]

No description provided.

[KonradStaniec]

@vitsalis I have just realised that I may have omitted one step in our versioning doc i.e according to https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow realeases should be doe from release branches like release/0.2.0 not directly from dev branches (as if now some would make merge pr to dev it would affect this pr). Wdyt about making branch release/0.2.0 and creating pr from there ?

Also one thing about release 0.2.0 maybe it is worth merging #204 before it as it adds logic of choosing best checkpoint submissions which in turn affects zonconcierge api. (Although it will require any node using 0.2.0 to start from scratch as it changes db format a bit) . wdyt @SebastianElvis ? (I will respond to all comments in pr and merge it tomorrow morning cet time)

[vitsalis]

Good idea @KonradStaniec . I think it is better if we do the release as the dev branch currently stands, as this is the version that is released on the demo right now (and we can't start it from scratch as we have started doing tests with our partners). wdyt? I will create a release branch and open a new PR tomorrow. We can immediately create 0.3.0 after #204 if it needs to be released soon.

[KonradStaniec]

@vitsalis sure then lets relesae 0.2.0 as it is. And release #204 with 0.3.0 👍

[vitsalis]

Created #217