resolve memory sloppyness and solidify Python access

[tomeichlersmith]

I am updating ldmx-sw, here are the details.

What are the issues that this addresses?

This resolves an issue seen when testing the updated OS image. LDMX-Software/dev-build-context#59

Check List

• I successfully compiled ldmx-sw with my developments
  • v3.5.0 <- tested by CI
  • v3.4.0
  • v3.3
  • v3.2 (with -DBUILD_DETECTORID_BINDINGS=OFF)
  • v3.1 (with -DBUILD_DETECTORID_BINDINGS=OFF)
  • v3.0 (with -DBUILD_DETECTORID_BINDINGS=OFF)
• I ran my developments and the following shows that they are successful.
  • successful means passing the tests in this case
• I attached any sub-module related changes to this PR.

Related Sub-Module PRs

• Solidify Python Access Framework#67
• use C API to get a python repr during failure Framework#68

[EinarElen]

On the tracing feature, I feel that ends up making an already relatively hard to read part of our codebase even harder. Would doing something like what I did in LDMX-Software/Framework#66 be an alternative?

[tomeichlersmith]

That's a good point - it does make the code pretty messy looking. I can implement the update you suggested to replace the tracing option.