Write an introduction to code reviews explaining how to make the best of a code review

[cloudappsguy]

Description

This PR adds new content to further enhance and describe the purpose and approach to code reviews.

PR Checklist

---

Use the check-list below to ensure your branch is ready for PR. If the item is not applicable, leave it blank.

• [X] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.
• [x] My code follows the code style of this project.
• [x] I ran the lint checks which produced no new errors nor warnings for my changes.
• [X] I have checked to ensure there aren't other open Pull Requests for the same update/change.

Does this introduce a breaking change?

---

• [ ] Yes
• [X] No

Any relevant logs or outputs

N/A

Other information or known dependencies

N/A

[github-actions[bot]]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.02s
✅ MARKDOWN	markdownlint	247		0	5.91s
✅ MARKDOWN	markdown-table-formatter	247		0	0.57s
✅ MDLINKCHECK	linkcheck	247		0	11.4s
✅ SPELL	cspell	258		0	11.84s
✅ YAML	prettier	10		0	1.45s
✅ YAML	yamllint	10		0	0.52s

See detailed report in MegaLinter reports

You could have same capabilities but better runtime performances if you request a new MegaLinter flavor.

• Click here to request the new flavor

_MegaLinter is graciously provided by _