58 - Automatically reformat code

[MellyGray]

What this PR does / why we need it:

This PR adds the automatic formatting to the repo using some pre-commit configurations. The pre-commits include:

1. Running the formatter
2. Running a typescript check to check the types
3. Fix all linter errors
4. Run the tests and check the coverage (95%)

A part from that:

• I added some changes to the ESlint and prettier config files to match the SPA formatting
• We were using a mix of jest, chai and sinon testing libraries, so I removed sinon and chai from the repo in favor of using only jest which simplifies the tests
• Since I added a coverage check to the pre-commits I had to add some tests to match the 95% coverage threshold
• I fixed some casting in some use cases because we were using the type casting as number instead of the real casting parseInt() and the tests were failing after changing from sinon assert to jest strict comparison.
• I rewrote some jest config files from javascript to typescript

Which issue(s) this PR closes:

• Closes automatically reformat code #58

Special notes for your reviewer:

There are a lot of changes, but these are just formatting changes so they shouldn't affect the features.

Suggestions on how to test this:

1. Visual inspection of the code
2. Make a change to the source code in your local environment and commit the change to check that the pre-commit checks are running as expected
3. Uncommit the test commit

[GPortas]

@MellyGray Can you please resolve conflicts?

Please, do not prioritize this PR if you have other pending feature-related issues, which should be our focus for the community day.

[MellyGray]

@GPortas merge conflicts resolved

One question, should we merge this PR here to fix the markdown library?

• fix: htmkToMarkdown library browser incompatibility #130

[GPortas]

@MellyGray

Yes, I just accepted and merged the PR. Can you please resolve the conflicts?

[GPortas]

I just tested the commit command as described adding a few malformed lines and I don't see any command logs or any changes to the pushed changes.

The pushed test changes are malformed:

I will revert the pushed changes if necessary.

@MellyGray

[MellyGray]

@GPortas did you ran npm install to install the pre-commit package?

[GPortas]

@MellyGray I missed that step, thanks!

[GPortas]

LGTM

GitHub action registry push is failing since I had to force push to a previous commit to revert test commits.