array-bounds checks are now fatal

[kroening]

Accessing an array out of bounds is undefined behavior, and hence, the assertions for this need to be fatal.

• Each commit message has a non-empty body, explaining why the change was made.
• n/a 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 1 line in your changes missing coverage. Please review.

Project coverage is 78.29%. Comparing base (621fe05) to head (8359aff).

Files	Patch %	Lines
src/ansi-c/goto-conversion/goto_check_c.cpp	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #8314   +/-   ##
========================================
  Coverage    78.29%   78.29%           
========================================
  Files         1722     1722           
  Lines       188448   188448           
  Branches     18452    18452           
========================================
+ Hits        147540   147553   +13     
+ Misses       40908    40895   -13     

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