standalone commands

[guymguym]

Explain the changes

1. Standalone commands
   1. Moved all standalone commands like nsfs to src/cmd/*.
   2. Add src/cmd/api command to send rpc api like the operator api command.
   3. Add also the web+bg+s3+hosted_agents+s3cat commands to src/cmd.
   4. Build single-executable from src/cmd/index with pkg so it can be used to run all the core services.
2. npm scripts:
   1. Add npm run db* scripts for running postgres on dev env.
   2. add --unhandled-rejections=warn to node commands in npm scripts.
   3. Reorganize npm scripts a bit.
3. Added docs/standalone.md with build and run instructions.
4. Fix a small problem in system_store that caused standalone processes to try and connect to the db even if it was not needed.

Issues: Fixed #xxx / Gap #xxx

1. NA

Testing Instructions:

1. In docs/standalone.md

[liranmauda]

some small comments + Love the cmd api 🙂

[liranmauda]

I would consider adding an example here:

Suggested change

	node src/cmd api <api_name> <method_name> [<params>] [options...]
	node src/cmd api <api_name> <method_name> [<params>] [options...]
	for example:
	node src/cmd api object_api read_object_mapping_admin '{
	"bucket": "name",
	"key" : "name",
	}'

[liranmauda]

Will we always have those?

[liranmauda]

maybe worth moving it to the config.js?
so it will be something like this:

Suggested change

	const http_port = process.env.PORT || '5001';
	const https_port = process.env.SSL_PORT || '5443';
	const http_port = config.PORT;
	const https_port =config.SSL_PORT;

[liranmauda]

Same as above, maybe move into the config.js?

[guymguym]

@liranmauda Thanks for the comments, these are about re-organizing the config/env, which I am very much interested in. But I will postpone this to next PRs. Thanks