C17 and C23 support

[kroening]

• Each commit message has a non-empty body, explaining why the change was made.
• Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• n/a My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 25 lines in your changes missing coverage. Please review.

Project coverage is 80.36%. Comparing base (10a14c9) to head (4531fa6).
Report is 2 commits behind head on develop.

Files with missing lines	Patch %	Lines
src/ansi-c/c_preprocess.cpp	0.00%	15 Missing ⚠️
src/ansi-c/scanner.l	0.00%	10 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #8620      +/-   ##
===========================================
- Coverage    80.38%   80.36%   -0.02%     
===========================================
  Files         1686     1686              
  Lines       206772   206796      +24     
  Branches        85       87       +2     
===========================================
- Hits        166213   166199      -14     
- Misses       40559    40597      +38     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.