docs: backport docs changes to v8 branch

[matthewmayer]

Backports to the following changes to v8 branch so that the main fakerjs.dev website can be updated without needing to wait for v9 release.

• docs: add donate links (docs: add donate links #2806)
• docs: use new X icon instead of twitter icon in social links (docs: use new X icon instead of twitter icon in social links #2825)
• docs: update roadmap for v9 (docs: update roadmap for v9 #2802)
• docs: improve contributing guide (docs: improve contributing guide #2747)

[netlify]

✅ Deploy Preview for fakerjs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	26d03cc
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/66270c4f3c77200008468aff
😎 Deploy Preview	https://deploy-preview-2847.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Shinigami92]

If we choose this strategy of backporting, we will never --ff-only again

[matthewmayer]

If we choose this strategy of backporting, we will never --ff-only again

Is it likely that we will need to merge into v8 in future? Most likely seems to be

• Minor website updates like this
• A super-critical bugfix requiring a 8.4.2 release

Is there an alternative to cherry-picking that keeps the history more clear?

[ST-DDT]

At this point I dont expect any ff-only merges to v8 anyway.