fix: [#4204] Fix remaining eslint warnings - enable ESLint config

[sw-joelmut]

Fixes #4204

Note: This PR lint script will successfully pass once all warnings are addressed. This is being tackled in separate PRs of the same issue.

Description

This PR updates the ESLint configuration adding new rules and disabling the ones regarding the any type, since it requires deeper analysis to not use the type. Moreover, we force the lint script to fail if there is at least one warning, preventing to introduce new ones in the future.

Note: we excluded the @typescript-eslint/no-explicit-any and @typescript-eslint/explicit-module-boundary-types to tackle those issues as a separate task, as they require deeper analysis and testing.

Specific Changes

.eslintrc.json

• Added node: true to the env property, due to not recognizing multiple NodeJs types.
• Disabled @typescript-eslint/no-explicit-any, @typescript-eslint/explicit-module-boundary-types and @typescript-eslint/ban-types, since there are many part of the source code that uses implicit or explicit any types, which requires deeper analysis to decide which type should use instead.
• Added jsdoc/require-jsdoc rule to warn the user when JSDocs are not provided in public classes, methods, properties and functions (ignoring private and protected).

Testing

The following images show the configuration working when there are/aren't errors.

[coveralls]

Pull Request Test Coverage Report for Build 2690427907

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.003%) to 84.483%

---

Totals
Change from base Build 2678878347:	-0.003%
Covered Lines:	19900
Relevant Lines:	22308

---

💛 - Coveralls

[tracyboehrer]

@sw-joelmut Can you take a look at this? Failing during yarn lint.

[ceciliaavila]

@sw-joelmut Can you take a look at this? Failing during yarn lint.

Hi @tracyboehrer, the lint check fails because there are new issues to fix. We'll fix them in a different PR and let you know.