TYPO3 Core

Some ideas:

- Clarify (shortly) who is allowed to review
- Note that many of the tasks are already covered by cgl and list is only for further common code-review steps
- Add a checklist of common code-review habits of experienced reviewers, see examples:
-- check exception timestamps
-- check declare strict
-- check ...
-- check if documenation matches implementation

Further, annotate that this documentation is subject to

- frequent change
- not claiming completeness
- stays a cheatsheet without in dept information to be easily adapted over time