Enable sanitizers for extended CI host build

[BenWibking]

PR Summary

Enable sanitizers (e.g., AddressSanitizer, UndefinedBehaviorSanitizer, etc.) for the extended CI host build. It is not enabled for the CUDA build, since CUDA does not support sanitizers.

Memory leak detection is currently disabled (does not work with OpenMPI, several unit tests have memory leaks).

Depends on:

• https://github.com/parthenon-hpc-lab/parthenon/pull/1113
• https://github.com/parthenon-hpc-lab/parthenon/pull/1111
• https://github.com/parthenon-hpc-lab/parthenon/pull/1108
• https://github.com/parthenon-hpc-lab/parthenon/pull/1112

PR Checklist

• [ ] Code passes cpplint
• [ ] New features are documented.
• [ ] Adds a test for any bugs fixed. Adds tests for new features.
• [ ] Code is formatted
• [x] Changes are summarized in CHANGELOG.md
• [ ] Change is breaking (API, behavior, ...)
  • [ ] Change is additionally added to CHANGELOG.md in the breaking section
  • [ ] PR is marked as breaking
  • [ ] Short summary API changes at the top of the PR (plus optionally with an automated update/fix script)
• [ ] CI has been triggered on Darwin for performance regression tests.
• [ ] Docs build
• [ ] (@lanl.gov employees) Update copyright on changed files

[BenWibking]

Tests are expected to fail until the issues are fixed in other PRs: https://github.com/parthenon-hpc-lab/parthenon/actions/runs/9522754529/job/26252926684

[BenWibking]

Probably need to disable LeakSanitizer for MPI runs due to the memory leaks in OpenMPI we can't do anything about...

[BenWibking]

AddressSanitizer and UndefinedBehaviorSanitizer run without workings, but some tests have memory leaks that cause LeakDetector to fail.

[BenWibking]

Rather than try to chase down every memory leak in the unit tests, I've just disabled memory leak detection entirely.

[Yurlungur]

Rather than try to chase down every memory leak in the unit tests, I've just disabled memory leak detection entirely.

I think that's the right thing but we should leave the memory leak test in place in the cmake so we can trigger it locally. Because someone should start trying to track these down over time. :)