DAOS-18529 test: expand/add a few suppressions

[janekmi]

{
   <insert_a_suppression_name_here>
   Memcheck:Addr8
   fun:atomic_load<__sanitizer::atomic_uint64_t>
   fun:NoTsanAtomicLoad<unsigned long long>
   fun:AtomicLoad<unsigned long long>
   fun:__tsan_go_atomic64_load
   fun:racecall
}
{
   <insert_a_suppression_name_here>
   Memcheck:Addr8
   fun:atomic_store<__sanitizer::atomic_uint64_t>
   fun:NoTsanAtomicStore<unsigned long long>
   fun:AtomicStore<unsigned long long>
   fun:__tsan_go_atomic64_store
   fun:racecall
}
{
   <insert_a_suppression_name_here>
   Memcheck:Value8
   fun:MemoryAccess
   fun:__tsan_read_pc
   fun:racecall
}
{
   <insert_a_suppression_name_here>
   Memcheck:Value8
   fun:atomic_store<__sanitizer::atomic_uint32_t>
   fun:StoreShadow
   fun:CheckRaces
   fun:MemoryAccess
   fun:__tsan_write_pc
   fun:racecall
}
{
   <insert_a_suppression_name_here>
   Memcheck:Addr8
   fun:func_add<unsigned long long>
   fun:NoTsanAtomicFetchAdd<unsigned long long>
   fun:__tsan_go_atomic64_fetch_add
   fun:racecall
}

Steps for the author:

• Commit message follows the guidelines.
• Appropriate Features or Test-tag pragmas were used.
• Appropriate Functional Test Stages were run.
• At least two positive code reviews including at least one code owner from each category referenced in the PR.
• Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

• Gatekeeper requested (daos-gatekeeper added as a reviewer).

[github-actions]

Ticket title is 'Too narrow __tsan_go_atomic64_load suppression and more'
Status is 'In Progress'
https://daosio.atlassian.net/browse/DAOS-18529

[daosbuild3]

Test stage NLT on EL 8.8 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17471/2/testReport/

[daltonbohning]

Do we know why NLT is marked as unstable? It seems unlikely, but is it possible this change is affecting something?

[kjacque]

Do we know why NLT is marked as unstable? It seems unlikely, but is it possible this change is affecting something?

Looking at the results, it seems like NLT just flagged some -DER_SHUTDOWN errors seen in the logs. No Valgrind errors. The log error stuff is a bit spurious in my opinion, it doesn't always seem to flag something meaningful.