[Merged by Bors] - Cleanup of Markdown Files and add CI Checking

[MinerSebas]

I have run the VSCode Extension markdownlint on all Markdown Files in the Repo.
The provided Rules are documented here: https://github.com/DavidAnson/markdownlint/blob/v0.23.1/doc/Rules.md

Rules I didn't follow/fix:

• MD024/no-duplicate-heading
  • Changelog: Here Heading will always repeat.
  • Examples Readme: Platform-specific documentation should be symmetrical.
• MD025/single-title
• MD026/no-trailing-punctuation
  • Caused by the ! in "Hello, World!".
• MD033/no-inline-html
  • The plugins_guidlines file does need HTML, so the shown badges aren't downscaled too much.
• MD036/no-emphasis-as-heading:
  • This Warning only Appears in the Github Issue Templates and can be ignored.
• MD041/first-line-heading
  • Only appears in the Readme for the AlienCake example Assets, which is unimportant.

---

I also sorted the Examples in the Readme and Cargo.toml in this order/Priority:

• Topic/Folder
• Introductionary Examples
• Alphabetical Order

The explanation for each case, where it isn't Alphabetical :

• Diagnostics
  • log_diagnostics: The usage of inbuild Diagnostics is more important than creating your own.
• ECS (Entity Component System)
  • ecs_guide: The guide should be read, before diving into other Features.
• Reflection
  • reflection: Basic Explanation should be read, before more advanced Topics.
• WASM Examples
  • hello_wasm: It's "Hello, World!".

[alice-i-cecile]

It would be nice to add this to the CI as well somehow, to avoid the churn of making commits like this periodically.

[MinerSebas]

I have added super-linter Github Action to check the Files.
This Action provides many different Linters, but for now, I only activated the Markdown Linter.

Other Linters that could be applicable here are YAML and Bash checks.
The HTML and Copy/paste detection do currently provided false positive Warnings.
A complete Report of the Repository can be seen here

As for the previously ignored Markdown Rules, they are now either fixed or explicitly marked as to ignore.

Edit:
I say the HTML check is a false positive because we have only 1. HTML file in the Repo, which is in the WASM Examples Folder.
The provided errors could be fixed, but I think it would be unnecessary to activate the check for 1. File.

[CleanCut]

Nice work. This looks like a good step in getting and keeping the markdown files clean. I especially like the random typos you caught and fixed in the process.

I have some suggestions I think would improve this even more, mostly based on my experience with GitHub Actions for CI. However, I'm not the gatekeeper and defer to @cart's preferences. 😄

[MinerSebas]

I added Documentation for the used Linters in the new ./docs/linters.md File.

The description for Clippy and rustfmt are lackluster because I was unsure what else to write, but I am open for suggestions.

[CleanCut]

I have some grammar/wording suggestions, but this looks great to me. Well done. 😄

Note to self: If this PR is merged first, I'll need to update docs/linters.md in #1387

[cart]

This looks good to me. I'm not the biggest fan of forcing "semantically correct" header types (# header comes first, then ## header, etc) over the "using header type for preferred style" approach we are currently using. But adding some structure to our markdown is a good idea and thats a pretty small thing to give up (and we can always fall back to html if we really need a particular style).

[cart]

bors r+

[bors]

Pull request successfully merged into main.

Build succeeded:

• build-android
• build (nightly, ubuntu-latest)
• build (stable, macos-latest)
• build (stable, ubuntu-latest)
• build (stable, windows-latest)
• build-wasm (nightly, ubuntu-latest)
• build-wasm (stable, ubuntu-latest)
• markdownlint