Stopgap solution for ignoring cppcheck false positives
Sometimes cppcheck flags up issues that don't exist, due to bugs in cppcheck itself. As a compromise between inserting inline suppression comments in such cases (which is undesirable because we'd probably want to remove them again later when cppcheck is fixed) and globally suppressing the diagnostics triggered by the bugs (which is undesirable because that renders those disgnostics unable to flag true bugs), we will be introducing a centralised list of false positive diagnostics, tuned to suppress the false positives as precisely as is permitted by cppcheck (short of specifying the line numbers, which are subject to change from revision to revision).
This will take some time to develop. In the meantime, as a stopgap solution, hard-code additional suppressions for select components into their included YAML files.
Currently based on top of !24 (merged) on the assumption that it will be merged first. This is because the two MRs touch the same lines, so otherwise I would have to untangle them and then put things straight back again as soon as !24 (merged) was merged.