Catch out-of-memory exceptions during propositional reduction

[tautschnig]

We already caught out-of-memory exceptions in some places in the solver back-ends, but not at the more global level of various propositional reduction steps.

Fixes: #727

• 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.
• 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 72.22222% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 79.92%. Comparing base (4fe3ade) to head (d3dee19).

Files with missing lines	Patch %	Lines
src/goto-checker/bmc_util.cpp	54.54%	5 Missing ⚠️
src/solvers/prop/prop_conv_solver.cpp	80.00%	5 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #8765      +/-   ##
===========================================
- Coverage    79.93%   79.92%   -0.01%     
===========================================
  Files         1698     1698              
  Lines       187698   187714      +16     
  Branches        73       73              
===========================================
+ Hits        150034   150039       +5     
- Misses       37664    37675      +11     

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