chore(project): raise versions of dependencies in order to address vulnerabilities

[KeiKey]

1. brace-expansion set to version 1.1.12 in order to address a vulnerability.
2. The following packages were upgraded to the recommended version
   "rimraf": "5.0.10" -> [Snyk] Upgrade mammoth from 1.7.1 to 1.9.0 #207
   "mammoth": "1.9.0" -> [Snyk] Upgrade rimraf from 5.0.5 to 5.0.10 #206
3. Playwright wasnt upgraded to the recommended version because of some reported issues I found online. Not worth the risk
4. @google-cloud/translate set to version 9.1.0 (rather than the recommended version) because of a warning that is in the lower versions.
   

[gamer496]

@KeiKey for point 3 regarding playwright, could you please share a brief reason and links as to what the risk is and why isn't it worth it?

[KeiKey]

@KeiKey for point 3 regarding playwright, could you please share a brief reason and links as to what the risk is and why isn't it worth it?

Before upgrading I checked online and came across some report of performance issues with version 1.50. Can't find it at the moment because not saved. Did a skimming of the reported issues on Github and came across some performance related issues there as well.

Snyk PR was about upgrading to a recommended version, not vulnerability related. Didn't go into details of the issues reported, just skipped it as not worth it.

[dcxn]

🎉 This PR is included in version 1.8.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀