Introduce bitst and bytest to avoid bit/byte mix-up

[tautschnig]

Use mp_integers with a unit to clarify when an mp_integer holds a number
of bits or a number of bytes. This makes sure that type-inconsistent
comparisons as fixed in #7411 result in compile-time errors.

• 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.
• n/a 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

❌ Patch coverage is 91.59664% with 50 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.40%. Comparing base (2e6200a) to head (e427ca9).

Files with missing lines	Patch %	Lines
src/util/pointer_offset_size.cpp	83.58%	11 Missing ⚠️
src/cprover/bv_pointers_wide.cpp	55.55%	8 Missing ⚠️
src/goto-programs/interpreter_evaluate.cpp	33.33%	6 Missing ⚠️
src/solvers/flattening/bv_pointers.cpp	73.33%	4 Missing ⚠️
src/ansi-c/expr2c.cpp	25.00%	3 Missing ⚠️
src/ansi-c/padding.cpp	93.87%	3 Missing ⚠️
src/goto-synthesizer/cegis_evaluator.cpp	60.00%	2 Missing ⚠️
src/memory-analyzer/analyze_symbol.cpp	89.47%	2 Missing ⚠️
src/util/config.cpp	84.61%	2 Missing ⚠️
src/analyses/goto_rw.cpp	88.88%	1 Missing ⚠️
... and 8 more

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #7413      +/-   ##
===========================================
+ Coverage    80.39%   80.40%   +0.01%     
===========================================
  Files         1688     1688              
  Lines       207403   207531     +128     
  Branches        73       73              
===========================================
+ Hits        166749   166873     +124     
- Misses       40654    40658       +4     

☔ 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.

[thomasspriggs]

Have you seen the approach taken to strong types here? https://www.fluentcpp.com/2016/12/08/strong-types-for-strong-interfaces/

This approach appears to have the following advantages -

• Templates are used to avoid needing a full cut-and-paste definition for each of the strong / unit associated types.
• Values are stored using containership rather than inheritance. This could side-step some of the potential issues with implicit upcasting.

[tautschnig]

Have you seen the approach taken to strong types here? https://www.fluentcpp.com/2016/12/08/strong-types-for-strong-interfaces/

This approach appears to have the following advantages -

* Templates are used to avoid needing a full cut-and-paste definition for each of the strong / unit associated types.

* Values are stored using containership rather than inheritance. This could side-step some of the potential issues with implicit upcasting.

Thank you for alerting me to this! This will require implementing more methods, but that's ok. I'll try this route.

[feliperodri]

LGTM.