#1148 include test coverage in actions

[akaiap]

Capturing coveralls results to appear in the README.md as the badge.

[dondi]

Generally looks good, but with some questions and a small potential revision before we proceed. Let’s address these then do another round

[dondi]

Is there a reason that this is calling require rather than import? The latter is the newer approach. Also, we should move chai.should() to after all of the import statements because the convention is to do all imports first before executing code

[akaiap]

• Since Mocha and the Node environment were still configured for CommonJS modules, using require made the test file run correctly under the regular CommonJS system. Switching to import would require the project to be recognized as an ES module (e.g., by setting "type": "module" in package.json).

• I will fix the import!

[akaiap]

I tested the build again after moving the chai.should() call below all the import statements. While the build still ran, it triggered warnings and linting errors.

• The issue is from an inconsistent module system, where ES Modules (import) are being processed before CommonJS (require). Moving chai.should() below the imports affects the execution order in a way that conflicts with the current module setup.
• Linting failures are due to ESLint 9 deprecating old configuration formats:
  ESLint now expects the "ignores" rule inside eslint.config.js instead of relying on the .eslintignore file.
  The "languageOptions" object no longer allows "ecmaFeatures", requiring an updated configuration.

We can go down to V8, but may still encounter the same error.