Rework the Client Resources chapter

[IchHabeHunger54]

Probably the biggest rework yet: the Resources chapter. I originally wanted to redo the entire Resources chapter at once, but given the sheer scope of that, I decided to split it into two: client and server. So client resources rework first it is.

This PR:

• Reworks the old Resources article, explaining the similarities and differences between assets/data and resource/data packs, as well as giving a brief overview about what datagen is.
• Adds a new article about I18n and L10n. This article replaces the I18n article in the Concepts section, the Component article in the Misc section, and the Language Datagen article.
• Adds new articles about particles and sounds. These articles replaces the Particles and Sounds articles in the Game Effects section, as well as the Sound Definition Datagen article.
• Adds a new article about textures and texture metadata.
• Adds several new articles in relation to models. These are rewritten, condensed and updated versions of the various mini-articles in the Rendering folder, the old articles in the Models folder, and the old Model Datagen article. Information about several previously undocumented features, such as baked model wrappers, was added as well.
• Does a fair bit of restructuring. The Rendering and Game Effects folders are gone, as their contents were merged into the Client Resources folder. The client datagen folder is gone as well; as a result, the server datagen was moved to the root of the datagen folder.
• Changes the Contribution Guidelines to use json5 for JSON blocks instead of js (to allow comments), as discussed on Discord. This guideline change is not applied to existing articles, only to new ones.
• Deletes a few now-unused pictures.
• Changes links as needed.

I made a few general design decisions in this PR that I'd like to outline here:

• Merge datagen articles into their respective "base articles" (lang datagen -> lang article, sounds datagen -> sounds article, etc.)
• Merge articles together. Instead of the previous 12 articles about model stuff, we have 4 now. These contain more content and are significantly longer, notably because I wanted to avoid single-page articles like the Tinting article. This philosophy can (and I imagine, will) be discussed, and I'm open to suggestions on what to change here.
• Use more examples. If there was one thing that was bad about the old docs, it was the lack of examples to work with. Just mentioning the methods is not a bad idea per se, but I see nothing wrong with also providing copy-paste base structures to work off. You need to insert your own names and stuff anyway. However, I do recognize that this contributes a lot to the length of some articles.

---

Preview URL: https://pr-62.neoforged-docs-previews.pages.dev

[neoforged-pages-deployments[bot]]

Deploying with Cloudflare Pages

Name	Result
Last commit:	ed4e02b12ca5787c40afec1b98b7ad7c1205635b
Status:	✅ Deploy successful!
Preview URL:	https://a0dc2c16.neoforged-docs-previews.pages.dev
PR Preview URL:	https://pr-62.neoforged-docs-previews.pages.dev