Add comprehensive fuzzing and sanitizer guide in English and German

[Easton97-Jens]

Motivation

• Provide a practical, language-neutral guide on combining coverage-guided fuzzing (libFuzzer) with sanitizers (ASan/UBSan/TSan) to improve test coverage and security for C/C++ projects.
• Explain limitations of classical unit/integration tests and demonstrate how fuzzing finds edge-case and undefined-behavior defects in input-driven components.
• Offer CI/CD integration advice and best practices so teams can operationalize fuzzing into PR and long-running pipelines.

Description

• Add two new documentation articles fuzzing_sanitizers_article_en.md and fuzzing_sanitizers_article_de.md containing conceptual background, practical examples, and references.
• Include runnable example fuzz_parse.cpp snippets, build commands such as clang++ -g -O1 -fno-omit-frame-pointer -fsanitize=fuzzer,address and -fsanitize=fuzzer,undefined,address, and CI usage examples like ./fuzz_parse -max_total_time=60 -artifact_prefix=./artifacts/.
• Document sanitizer roles (ASan/UBSan/TSan), fuzzing modes (random vs coverage-guided), typical bug classes discovered, CI strategies (PR smoke-fuzzing vs nightly campaigns), and recommended best practices.

Testing

• No automated tests were run because this change only adds documentation files and no production code was modified.
• Documentation changes are intended for inclusion in the repository as reference material and can be validated by downstream doc-build or linting pipelines if present.
• No test failures occurred because no tests were executed.

---

Codex Task