[up coming] migrate frontend into neetbox build

[visualDust]

Upcoming feature including frontend

Once user run bash command neet init and import neetbox in their python projects, neetbox should be able to trace down hardware and logging, as well as other things including up coming "ploting" features, in a frontend called neetbox frontend. neetbox frontend is an exciting feature in the next release.

Users may set up project to connect to the same neetbox backend (localhost by default) in their workspace config file neetbox.toml, and their logs via neetbox.logging.logger would print into not only console and files, but also frontends. Uses will also see CPU usage and platform information showing in charts on neetbox frontends. Uses can also register custom functions via neetbox.daemon.action (thats also an upcomming feature) and see a button on the frontend, they can trigger the function in their python code by pressing the button on the frontend.

Basically a neetbox client means a project running with import neetbox. users can run projects on multiple machines and let them connect a neetbox server, which gathers information and serves frontend.

But now, we are happy to announce that neetbox client, neetbox server, and neetbox frontend are going to merge into a single package. That is, the new ALL IN ONE neetbox. Once use launch a project with neetbox, neetbox generally check the server address. if it is localhost, neetbox will automatically launch a neetbox backend and frontend locally. If you want to run a neetbox server on cloud servers, you can launch it by bash command neet serve, and edit your projects' neetbox.toml to let them connect your server, the frontend will be launched on your server too.

frontend is on the way, @lideming is in charge and it should not take so long. See new features with frontend in the next release.

[visualDust]

#77

[visualDust]

in #76 (0a391e5), we added run id columns to history db and server as well as client python api, to distinguish runs. On every run of a neetbox project, neetbox generates a new run id. The original intention of adding this design was due to tensorboard-sometimes users need to view the data generated by each project run separately.
However, we do support static run id. if user add run id to config file neetbox.toml generated by cli, the project will use this specific run id on every launch. Besides, users should be able to choose whether to distinguish each run in frontend(frontend has not started on run id yet and we have a lot of freedom about how to design this feature at user level).