integrate client-nodejs with bazel build system

[vmax]

Why is this PR needed?

So we are able to test client-nodejs with bazel

What does the PR do?

Migrates client-nodejs to bazel

Does it break backwards compatibility?

no

List of future improvements not on this PR

publishing artifacts to npm

Implementation details: short version

We need to have correct imports in generated *_pb.js files and then we need to put generated files to same locations they would have been in if compiled by npm

Implementation details: extended version

• _proto_gen genrules take proto files and strip protocol/session import statements using generate_js.sh
• generated_node_lib is generated from those protos (a set of *_pb.js and *_grpc_pb.js files). A modified version of grpc/grpc is used so file is generated even if there are no services in files
• generated_node_lib_transformed moves generates js files to appropriate locations so require() statements in client's sources are satisfied
• grakn combines all js files into one package
• grakn_dummy_binary is needed to generate a tar.gz bundle with all dependencies
• jest_tests runs tests with jest. We need to use .tar.gz bundle because jest cannot handle symlinks bazel is producing relevant issue and they refuse to merge PR that fixes it. This method resembles what has been done for client-python (we generate zip module there)

[haikalpribadi]

This PR adds 8K lines of package-lock.json, @vmax. I think we should remove it.

[haikalpribadi]

and why do we need lots of manual genrules in client-nodejs/BUILD, @vmax ?

@marco-scoppetta will review this instead

[vmax]

Replaced with #25