fix: supplement and organize the dependency and readme files for each kernel

[birdflyi]

Fix https://github.com/X-lab2017/open-digger/issues/1578

Purpose

Supplement and organize the dependency requirements.txt files and README.md files for each kernel; Unified the startup method of all kernels.

Method

• Supplement and organize the dependency requirements.txt files and README.md files for each kernel

  • Check if the dependency requirements.txt file or README.md file of each kernel exists and locate their location. (see https://github.com/X-lab2017/open-digger/issues/1580#issuecomment-2185631697)
  • Mutual reference and supplementary content between documents
  • Reorganize the position of documents

• Unified the startup method of all kernels

  • Extract similar description patterns in the contents of README.md files

  • Extract the universal Dockerfile pattern with arguments for kernels

  • Adjusting the kernel's interface related to startup

Feature

Kernels

kernel_name	kernel_src_dir	kernel_requirements	kernel_readme	kernel_build_run	kernel_base_img
node.js	"./src"	"./package.json"->"dependencies"	"./sample_data/README.md"	"./package.json"	"./package.json"->"scripts"."notebook"->"docker pull {kernel_base_img}"
python	"./python"	"./python/requirements.txt"	"./python/README.md"	docker command	"continuumio/miniconda3"
python_v2	"./python_v2"	"./python_v2/requirements.txt"	"./python_v2/README.md"	docker command	"continuumio/miniconda3"
pycjs	"./pycjs"	"./pycjs/requirements.txt"	"./pycjs/README.md"	"./package.json"	"./package.json"->"scripts"."notebook"->"docker pull {kernel_base_img}"

Results:

• Each kernel has its own dependency file and README.md file.
• Python kernels have the same file directory structure and startup method
  • Python kernels use the same Dockerfile in the root work directory.
  • Python kernels use the similar startup method with their own kernel_src_dir and kernel_base_img arguments.
  • *A npm run notebook-pycjs command is added into package.json for the kernel pycjs since it has a similar dependency pattern with the kernel node.js.
• All kernels have been well tested in windows 11 v.23H2 and cygwin Linux simulation environment.

Extra: Fixed some minor bugs in notebook/node_vm2_pycaller.ipynb, python_v2/db/clickhouse_wrapper.py and python/db/clickhouse.py. The package.json settings makes the startup of kernel pycjs as easy as the kernel node.js. The startup method of kernel pycjs:

1. Enter the root workdir: cd open-digger
2. Build js environment(execute only on the first run): npm install
3. Build docker image and run a container: npm run notebook-pycjs

[frank-zsy]

I am not quite familiar with Python kernel, can you check on this PR? @Peng99999

[Peng99999]

@frank-zsy I've already tested it, and this PR can be merged. Thanks to @birdflyi for this work, the issue #1580 mentioned in the previous weekly meeting have been resolved. 👍