Update test workflow

[JimiC]

• Upgrading node version
• Allow fail on non-essential node versions
• Cancel workflow when another commit is made on the same branch
• Run jobs on batch of 3
• Improving code coverage workflow
• Upload code coverage directly if development is being done withing the repo (only the dev team is allowed to do that), otherwise use artifacts and use another workflow to ensure no secrets are leaked

Note: This is part 1 of 2 for the dependencies update. This PR must be merged first before the Dependencies Update PR can be submitted.

[JimiC]

@robertohuertasm No idea why the PR has no access to secrets although the checkbox for "Allow edits and access to secrets by maintainers" is checked.

[JimiC]

Just found out why access to secrets worked on my testing and not in the PR.
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/

Will look for a potential workaround or revert to the existing code coverage workflow.
Update: Found a workaround

[JimiC]

@robertohuertasm If you find some time pls do a review so we can merge this PR and iron out any issue that may lurk.

[JimiC]

Oh crap. Now I have to work on the second part of the update. @robertohuertasm Pls hold any release until I submit the rest.

[robertohuertasm]

What do you need to do? Maybe I can help you with that.

[JimiC]

I have done it when I worked on the workflow update. I just have to bring it up to speed. Some rebase and potential fixes for issues that may have arise since. Hopefully I can resolve it in a couple of hours.

[robertohuertasm]

Ok, I'll try to fix some pending PRs in the meantime.