[Core Plugin] Release Plugin along with Neo-Node

[Jim8y]

Summary or problem description
A good design of having neo plugin, but now it only cause the system hard to use, hard to maintain, hard to setup. We should consider to remove it.

Do you have any solution you want to propose?
To ensure that existing user can still have the same experience, there is no need for us to remove plugin structure, at lease for now. We can release the plugins along with neo-node, and by default we disable those plugins, user can enable them in a config file or from command line.

Why so?

In this way, we only need to release one package, that is neo-cli, user does not need to install plugins manually, for us developers we can directly build our updated plugin into neo-cli and integrate test it with neo-cli, otherwise we will need to manually copy the dll file to the neo-cli folder.

Where in the software does this update applies to?

• CLI
• Plugins

[dusmart]

Will custom plugins be impacted?

[Jim8y]

Will custom plugins be impacted?

No, custom plugins can still be installed as usual. Just built in plugins will be released along with the node, disabled by default of cours.e