XML trace test: do not hard-code pointer bit pattern

[tautschnig]

The exact bit pattern of the pointer is irrelevant to this test. It's
just the content of the underlying array that matters.

• 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

Merging #6147 (437420d) into develop (b1fcc9a) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##           develop    #6147   +/-   ##
========================================
  Coverage    74.95%   74.95%           
========================================
  Files         1447     1447           
  Lines       158208   158197   -11     
========================================
+ Hits        118577   118580    +3     
+ Misses       39631    39617   -14     

Impacted Files	Coverage Δ
src/solvers/flattening/boolbv.h	76.19% <ø> (+6.62%)	⬆️
src/solvers/flattening/bv_pointers.cpp	82.70% <0.00%> (+1.54%)	⬆️
src/ansi-c/c_typecheck_expr.cpp	60.26% <0.00%> (+0.14%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 78a08ce...437420d. Read the comment docs.