Improve memory testing

[dani-garcia]

Type of change

- [ ] Bug fix
- [ ] New feature development
- [x] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

Improve how the memory-testing crate does some things:

• Compile and run the process in release mode, to better match what our final artifacts will do.
• Improve the structure of Cases struct, now the values that we want to look up in memory are generic, which greatly simplifies the analyze-dumps binary.
• Removed the test string from the table output, if we don't find the test string in the dump we assume the dump is invalid and return directly.
• Instead of waiting a predefined amount of time, the dump program now waits for the program to notify that it's ready, which speeds up the operations a bit.
• Use black_box instead of just printing the values, to ensure the compiler doesn't optimize them out.

[github-actions]

Checkmarx One – Scan Summary & Details – 13fb89cb-ea74-4956-bb30-cbb6eaebdc5e

No New Or Fixed Issues Found

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.74%. Comparing base (a2495b7) to head (b335273).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #766   +/-   ##
=======================================
  Coverage   61.74%   61.74%           
=======================================
  Files         173      173           
  Lines       10934    10934           
=======================================
  Hits         6751     6751           
  Misses       4183     4183           

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