Keep using the latest MyGet Neo package when pushing a new PR

[superboyiii]

Summary or problem description
Currently the repo is using stable and released Neo from Nuget.org until a newer one comes out, then neo-modules can check and fix incompatilbe changes. This is risky and it puts every potential issues and fix into the end before release. It's not good to check all changes in the end and easy to forget sth.

Do you have any solution you want to propose?
We already have MyGet Neo package for each commit, it's better to update the latest Neo when pushing a new PR, then we could catch changes timely.

Where in the software does this update applies to?

• all plugins even Neo-CLI

Need your opinion
@roman-khimov @shargon @vncoelho @cschuchardt88 @AnnaShaleva @Liaojinghui

[Jim8y]

I think this repo will also be added to the mono-repo, @roman-khimov, so it will directly use the neo-vm and neo-core source code.

[shargon]

This will be solved with mono-repo.