[CI] Integrate Cppcheck for static code analysis

[iamazeem]

• Add .cppcheck file for project configuration
  • Cppcheck manual: https://github.com/danmar/cppcheck/blob/main/man/manual.md
• Add shell script to run cppcheck and generate XML and HTML reports
• Configure CI workflow to run cppcheck script
  • Upload XML and HTML reports as artifacts
  • Add navigable Cppcheck summary in the CI's step summary as Markdown
• Update .gitignore
• Resolves [CI] Integrate Cppcheck for static code analysis #195

Signed-off-by: Azeem Sajid [email protected]

[iamazeem]

@liquidaty: Please review. Thanks!

Latest workflow run: https://github.com/liquidaty/zsv/actions/runs/11083488307
XML report: https://github.com/liquidaty/zsv/actions/runs/11083488307/artifacts/1990625061
HTML report: https://github.com/liquidaty/zsv/actions/runs/11083488307/artifacts/1990625087

[iamazeem]

@liquidaty: Please review.

Markdown summary added with navigable links to source and CWEs:
https://github.com/liquidaty/zsv/actions/runs/11093601828/attempts/1#summary-30820086884

Now, we have XML and HTML reports that are uploaded as artifacts.
In addition, we have this Markdown summary.
LMK whether we need to keep all of these.
Thank you!