Add explanation for Component and ComponentContents

[tmvkrpxl0]

Internalization document only just mentions Component and ComponentContents without proper explanation. Although I don't fully understand these two, I've decided to come up with my own section for it.

---

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

[ChampionAsh5357]

Excluding grammar, this needs more information on the types of components along with associated examples. It also makes more sense for components to be a separate page as the only contents that deals with localization is TranslatableContents.

[tmvkrpxl0]

Sorry for multiple force push, I tried to turn my last commit as verified, but it doesn't seem to work.
I have made Components page into separate one and moved into different directory.
This time there would be less grammar error, I double checked with external tools.

[ChampionAsh5357]

This should also talk about why most users should only use translatable contents to support localization in other languages.

[neoforged-pages-deployments]

Deploying with Cloudflare Pages

Name	Result
Last commit:	0332500a24c37e1b2f6999e1369724a77398f3a8
Status:	✅ Deploy successful!
Preview URL:	https://92d7e5e5.neoforged-docs-previews.pages.dev
PR Preview URL:	https://pr-4.neoforged-docs-previews.pages.dev

[tmvkrpxl0]

w h a t
There's auto deploy for PRs too? Wow

[ChampionAsh5357]

Lot of missing articles.

Additionally, we should be using text wrapping for lines, so paragraphs should be on a single line, not spread across multiple.

[ChampionAsh5357]

Last batch I believe. Once again, any paragraphs should be combined into one line, not one line per sentence.

This:

This is a sentence. This is a second sentence.

Not this:

This is a sentence.  
This is a second sentence.

[ChampionAsh5357]

Missed a few more english stuff and a page link, but it should be done after this...probably.

[ChampionAsh5357]

Everything seems fine now, let's see if I can merge it on mobile