docs: Rework naming convention and status description requirements

[mattmaniak]

Description

Type(s)

• Game page addition
• Game page modification
• Other wiki edit

Verification

Have you

• Followed the contribution guidelines?
• Ran ./scripts/generate.mjs?
• Ran ./scripts/lint.mjs?
• Checked spelling and grammar?
• (If applicable) Provided documentation for a game not working? (i.e. detailing what happens when the game doesn't work?)

Most likely the biggest PR of all times here but it addresses some things that make docs navigation, maintenance and lack of some details issues:

• Abbrevations are no longer allowed and present. As the game titles are sorted alphabetically via markdown files names it's getting messier and messier with a proper ordering - some titles were completely somewhere else than expected. Also with a growing database of tested games, acronyms make things harder to maintain. Not everyone of us knows each acronym of each game and while we can easiliy search them via code editor it still gets messy when some markdown files are acronyms, some are partial acronyms and some are not at all. This PR provides a consistency of no acronyms with an exception of "goty" - Game of the Year which is well known.
• Every know issue occurence that was listed before on a game page was moved under a [!WARNING] heading to keep any games issues in one place.
• Names of the games were updated and taken directly from Steam for consistency. An idea has started here. It may be automated in a future using a Steam API most likely where a GitHub Actions would check for the game name using a given Steam app ID.
• Minor formatting issues were applied for a better consistency and legibility.
• Nothing new has been added to games performance info apart of the broken REDlauncher in The Witcher 3.

Any maintainer feedback is welcome as it is a huge change and it is better to discuss it before deploying but I hope that my idea and implementation have a solid background.

[JoshuaBrest]

I can add a lint feature later.

[mattmaniak]

I can add a lint feature later.

You're welcome :) @hahayupgit any thoughts on PR?

[hahayupgit]

Overall looks good! Minor things I'm going to go in and fix, and then approve. Great job!!!!

[hahayupgit]

Fantastic PR!