fix: switch from mocha and chai to the jest

[magicmatatjahu]

Description

• switch from mocha and chai to the jest. Simple reason. Mocha and chai (specifically, a ts-node which transpiles code from TS to JS) has a some problems with importing ESM. I found that problems when I started writing tests for feat: integrate new parser-js #347 and new parser uses new module syntaxes. We still need chai in devDependencies, because @oclif/test uses it underneath.
• bump @oclif/core to the latest ^1.18.0 version.

Related issue(s)
See more #347

[derberg]

sorry but let us first merge #221

[magicmatatjahu]

@derberg Done, could you check again? :)

[magicmatatjahu]

@derberg ping, ping :P

[derberg]

can you share why changes in [src/base.ts](https://github.com/asyncapi/cli/pull/353/files#diff-440b55a9ff9e0486020fc49197f3278d14446306fc0c5d5107b48139c20bfda6) were needed? and also is oclif upgrade necessary, related to refactoring of tests?

[magicmatatjahu]

@derberg When I switched to the jest, oclif doesn't recognized errors from stderr but it throws to the stdout, so I log errors by this.logToStderr(${e.name}: ${e.message}); line.

Related to the bump of oclif - I made a bump along with the transition to the jest. Between 1.11 and 1.18 there is nothing big that will cause a breaking change in our cli.

[derberg]

lgtm, but because prod dependency got updated, we should release it as fix: and indicate it clearly in the description that it is not only refactor of tests really, but core dependency got also upgraded.

I approve but please make sure to make proper adjustments before merge

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[magicmatatjahu]

/rtm