[PRODENG-211] integrate JS-API with monorepo (part 1)

[DenysVuika]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation
• Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)

What is the new behaviour?

integrate JS-API project into the monorepo

• build (nx build js-api)
• lint (nx lint js-api)
• test (nx test js-api upload suite disabled and needs investigations)
• integrate with GHA unit testing
• publish to npm
• update scripts/update-version.sh
• update scripts/github/build/npm-check-bundles.sh
• review the Sonar Cloud report and fix what's possible
• tsconfig paths for other libs
• remove JS-API upstream GH worfklow and corresponding scripts
• switch to node.js assert instead of chai where posible
  • remove @types/chai
  • remove @types/chai-spies
  • remove chai
  • remove chai-spies

After the merge of part 1:

• review the upstream adf on apps
• ensure the lib is published to GitHub package registry

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:
https://alfresco.atlassian.net/browse/PRODENG-211
https://alfresco.atlassian.net/browse/ACS-6231

[sonarqubecloud]

SonarCloud Quality Gate failed.   

8 Bugs
0 Vulnerabilities
2 Security Hotspots
115 Code Smells

No Coverage information
3.3% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[mauriziovitale]

Please make sure the code is up to date with the latest commit on the js api