Replace faker with the new @faker-js/faker stable fork

[rubenmoya]

Why this feature is required (specific use-cases will be appreciated)?

This tweet from Romain sums up what happened:

It seems that @marak has been hacked.

Faker repository is gone, release 6.6.6 which is empty.
At least, it seems nothing malicious was added inside this release.

It could have been really worse.https://t.co/z7RjyGOA64https://t.co/5LIfjdt1Pp

— Romain Lanz 🦊🌖 (@RomainLanz) January 5, 2022

A lot of forks were created the days after that, but some people worked on unifying them and dealing with all the problems:

For the last 3 days I've been working on Faker and dealing with the fallout. The package. The docs. The Open Collective. Please follow the @faker_js account for an official statement in the next day.

Maintainers are now @damienwebdev @Shini_92 @_prisis_ @mmahalwy griest + myself

— jess (@_jessicasachs) January 12, 2022

This are the links to the project:

Repository: https://github.com/faker-js/faker
Twitter: https://twitter.com/faker_js

Have you tried any other work arounds?

We could just keep the current version, but I just wanted to have this issue as a reminder that we need to update it.

Are you willing to work on it with little guidance?

Sure!

[RomainLanz]

Hey @rubenmoya! 👋🏻

I believe @thetutlage planned to write another Faker-like package with a better API, but I agree that we should migrate off Faker in the meanwhile.

I will look at this new fork and see how it can be integrated without breaking changes.

[thetutlage]

Yeah, if this new package is a drop-in replacement, then we should go ahead and update the dependency

[rubenmoya]

Do you want me to give it a try? Or do you prefer to change it yourselves?

[thetutlage]

Sure! Feel free to send a PR for the same

[RomainLanz]

Are you still willing to work on it @rubenmoya?

[rubenmoya]

I'm sorry I do not have enough time right now to focus on it :(

[thetutlage]

Done in #791