chore: upgrade dependencies

[hacknug]

🔗 Linked issue

No issue but this is what npm audit returns:

29 vulnerabilities (2 low, 13 moderate, 11 high, 3 critical)

❓ Type of change

• [ ] 📖 Documentation (updates to the documentation or readme)
• [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
• [ ] 👌 Enhancement (improving an existing functionality)
• [ ] ✨ New feature (a non-breaking change that adds functionality)
• [x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• [x] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

A client's project is stuck using nuxt v2 and some of the warning during npm audit come from this package.

I updated the dependencies only using npm audit fix --force to avoid as many changes as possible. This fixes all of the issues reported by npm audit (running without --force leaves us with 10 vulnerabilities (1 low, 5 moderate, 4 high)).

I also removed yarn.lock since it seems there already is a package-lock.json that was touched more recently.

All tests pass but since both changes are major updates, merging this could not be as straightforward as I'd like.

Feel free to merge, close, or request changes as you see fit 👍