Explain blocks and blockstates in more depth

[IchHabeHunger54]

This PR improves and expands on the explanation of blocks and blockstates. More specifically, it:

• Adds more information on how every block and every blockstates exists in memory once, and why calling new Block() is a bad idea
• Adds more information on when to use blocks, when to use blockstates, and when to use block entities
• Adds a brief explanation of blockstate JSONs and block model JSONs, with references to the Resources section
• Adds information about how most methods expect a BlockState rather than a Block, and why that is the case
• Adds more information about BlockState's most important usecases, specifically BlockState#getProperty, BlockState#setProperty, Level#getBlockState and Level#setBlock
• Adds information on the update flags for Level#setBlock
• Removes the historical section about block metadata, as it is irrelevant to the average modder
• Removes the disclaimer about optional registration, as that is better suited for the registration section
• Rewords some sections and fixes some grammar and spelling issues

---

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

[neoforged-pages-deployments]

Deploying with Cloudflare Pages

Name	Result
Last commit:	a8b4c53e22a511c2a491b4abfbd71d7b63aeb385
Status:	✅ Deploy successful!
Preview URL:	https://b248ddeb.neoforged-docs-previews.pages.dev
PR Preview URL:	https://pr-21.neoforged-docs-previews.pages.dev

[ChampionAsh5357]

More explanations and examples are necessary. Also, if you are rewriting the page, use the notes in the new contribution guidelines.

[IchHabeHunger54]

I was under the impression that we held to the old project's standard of not including example code in the docs. As I understand it, this has changed, so I will update the PR accordingly.

[ChampionAsh5357]

Yeah, generally prefer pseudocode like java with comments over exact examples unless necessary. The guidelines should show an example

[IchHabeHunger54]

Rewrote major parts of it to consider the feedback, examples have been added. I also added a WIP method reference page that I will finish tomorrow (hopefully). Converting to draft for now.

[IchHabeHunger54]

I also dismissed most of the feedback since I fixed most of it when rewriting ("fixed" from my point of view). If there are problems with it still, feel free to re-add feedback as needed.

[ChampionAsh5357]

Wow, this has improved so much. In general, I think the detail is great, but there are instances where you are straight up defining the method. That's fine when comparing between vanilla and NeoForge, but I believe most of those descriptions should go into Parchment or NeoForge itself. The interaction workflow meanwhile, can probably stick around.

Anything else I still need to think on what makes sense in the docs. I'm now marking this as the issue to resolve the block portion of #20

[XFactHD]

Final thing I missed yesterday, finally good to go from me when that's fixed

[ChampionAsh5357]

Looks good. Will try to merge on phone.