goto-analyzer: --show-local-bitvector

[kroening]

This adds --show-local-bitvector as a task to goto-analyzer.

• 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).
• 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 81.25000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 78.34%. Comparing base (f9a7807) to head (1e50663).
Report is 27 commits behind head on develop.

Files with missing lines	Patch %	Lines
src/goto-analyzer/goto_analyzer_parse_options.cpp	81.25%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #8546      +/-   ##
===========================================
- Coverage    78.38%   78.34%   -0.04%     
===========================================
  Files         1729     1729              
  Lines       200151   200307     +156     
  Branches     18244    18247       +3     
===========================================
+ Hits        156883   156934      +51     
- Misses       43268    43373     +105     

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

[kroening]

It's debatable whether we should give this analysis a different name. E.g., "pointer flags", or the like.

[tautschnig]

It's debatable whether we should give this analysis a different name. E.g., "pointer flags", or the like.

Possibly, but that seems unrelated in that we'd want to rename not only this newly added command-line option.