Automate publishing development versions of the package

[vsbogd]

This issue is result of discussion in PR https://github.com/singnet/platform-contracts/pull/51 (see PR https://github.com/singnet/snet-cli/pull/76 for previous related change).

Solution proposed in PR https://github.com/singnet/platform-contracts/pull/51 requires additional compilation and package building when platform-contracts package is deployed as dependency.

Solution proposed in PR https://github.com/singnet/snet-cli/pull/76 requires developing dev dependency installation script and .circleci scenarios modification for each repo which uses platform-contracts.

So we need to design and develop packaging solution which doesn't have these disadvantages or agree with one of the approaches above.

[vsbogd]

One possible way is to publish new github release each time when we need new version globally.

It can be published manually for instance using some script. Or we can add publishing step to the circleci script which handlea changes in master branch. The only problem I see is authentication.

[vsbogd]

I have added first development release for platform-contracts manuall release v0.2.2

Commands to create release tarball:

VERSION=0.2.2
npm install
npm run compile
npm run package-npm
cd build
mv npm-module singularitynet-platform-contracts
tar czf singularitynet-platform-contracts-${VERSION}.tgz singularitynet-platform-contracts

[astroseger]

Should we close it?

[vsbogd]

I would say we should automate release publishing first then we can close it.

[astroseger]

Now snet-cli and daemon use development releases in order to get ABI of contracts. But it should be noted that snet-cli gets address of Registry and AgentFactory from networks/*.json files from npm-package. Which is might be not optimal for tests...

[vsbogd]

We can remove all network addresses except main and testnet from published versions.