Added a hybrid module for node

[avifenesh]

Fix for issue 1116:
Some of the client of our package are using Ecma and some Commonjs as they're JS standard.
In order to make it available in both standards, iv'e created an hybrid build, in which the user will get the build fits his need base on his standard.

Added tests of basic usage (the main test that is needed is to see whether its possible to use the built package in the JS projects of different standard type).

Added the tests to the Node workflow.

Changes explanation in a bit more details:
We are using TSC in order to translate our package to JS.
So instead of using one file of tsconfig.json for the rules of the translation we are using a hybrid method -
tsconfig-base as the general tsconfig file, which the other will inherited from.
tsconfig-cjs for commonJS build with commonjs as the target of translation and and tsconfig for ECMA build with ECMA as the target of translation.

While running build we run two different builds - one will use tsconfig and will translate the package into build-ts/mjs, and the other will use tsconfig-cjs and will translate the package into build-ts/cjs.

In our package.json we are adding the rule -

    "exports": {
        ".": {
            "import": "./build-ts/mjs/index.js",
            "require": "./build-ts/cjs/index.js"
        }
    },

In which depends on what type of import statement the user choose (import in ECMA, and require in commonJS), the user will get the fitting package to his standard.

As part of the build we are running the fixup_pj_files_for_build_type script -
This script add "type" and "types" values to the different package.json that been created for mjs and cjs with the fitting values.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[shachlanAmazon]

please add to the PR description (or into DEVELOPER.md) an explanation of the how, not only the what. As it is, the PR is a collection of scripts, and it's very hard to understand how the pieces combine and what they do.
And, of course, fix CI.

[avifenesh]

please add to the PR description (or into DEVELOPER.md) an explanation of the how, not only the what. As it is, the PR is a collection of scripts, and it's very hard to understand how the pieces combine and what they do. And, of course, fix CI.

Added explanation for both PR and developer.md, please let me know if the explanation is clear and helpful @shachlanAmazon

[shachlanAmazon]

great work!
@barshaul thoughts?
IMO we should release a version after this will be merged.

[shachlanAmazon]

please also update the CHANGELOG.md file

[barshaul]

Nice!

[shachlanAmazon]

LGTM.