NSFS | NC | NC Coretests changes - PR 2/3

[romayalon]

WIP - This PR is dependent on merging #7719

Explain the changes

1. Makefile - added run-nc-tests makefile rule for running nc_index.js tests file.
2. test_utils.js - added a helper function for get_coretest_path() that chooses coretest/nc_coretest path by process.env.NC_CORETEST.
3. nc_coretest.js - config_dir, storage, and other setups and starting nsfs.js process, added mapping between rpc_client calls and manage_nsfs commands or other mocks.
4. nc_index.js - added NSFS relevant test files.
5. test_bucketspace.js - added skips by process.env.NC_CORETEST of non-relevant tests, and different error_codes.

Issues: Fixed #xxx / Gap #xxx

1. Gap - nc_index.js contains commented test files that needs to be added as well.
2. github action for running nc_index.js

Testing Instructions:

• Doc added/updated
• Tests added

[naveenpaul1]

A comman doubt : - How this different from the normal test?

[naveenpaul1]

@romayalon are we validating this account update anywhere else? just a doubt

[romayalon]

on the tests, this function equal to the rpc function - update_account_s3_access(), the difference here is that on Non containerized version we don't have RPC server so we do the update by running manage NSFS cli calls instead and return rpc like response.

[romayalon]

@naveenpaul1 The regular Coretest runs noobaa endpoint (and other components of noobaa core) and then a test can run full s3 flow.
NC Coretest runs nsfs.js instead of running the endpoint and by that, we run the NC code. Then a test can run full s3 flow on NC environment. I hope it makes it clearer, let me know if there are more questions.

[naveenpaul1]

LGTM