Short-term plan for this binding

[waynexia]

Task list for the first milestone.

The first milestone should:

• Be generally available for common SQL queries.
• Have a fundamental docs API and can be released to npm.js automatically
• Have the basic config API for essential configs.
• Define a (unstable) data API (maybe on top of https://arrow.apache.org/docs/js/ ?)

Tasks:

• Expose configuration APIs (SessionContext)
• Define and expose RecordBatch 1368bc5
• Support GCS and Azure Bolb
• Support more kinds of queries (fix them in the "upstream" datafusion)

[waynexia]

In addition to the to-do list above, I also want to gradually bring this project to a relatively stable release rhythm, such as regularly synchronizing upstream updates or releasing. This can ensure that the project has a basic vitality.

My personal goal for this project is to make it an official part of DataFusion (ref to apache/datafusion#13815), just like the Python binding. People can easily use DataFusion for computations in more scenarios. At the same time, this project already has several application scenarios (datafusion-wasm-playground, parquet-viewer, or the ongoing one apache/datafusion#13818), ensuring that the basic release rhythm can also facilitate existing projects to use it better.