Add thread sanitizer test in CI

[lucafedeli88]

This PR adds a thread sanitizer test in CI.

Specifically:

• a new clang_sanitizers.yml workflow file is created
• the pre-existing UB sanitizers test is moved from ubuntu.yml to clang_sanitizers.yml workflow
• a thread sanitizer test is added. This test needs clang-17. Therefore, for this test, we use a Ubuntu 23.10 container and we install clang-17 with the instructions added to a new dependencies file (clang17.sh).
• the test consists in compiling WarpX with the thread sanitizer and in running the laser_acceleration example in 1D,2D,3D, and RZ, as well as the embedded_circle example in 2D (I suspect that there might be a race condition in the code relevant for this example due to the frequent random failures of this test in CI). In all cases the serialization of initial conditions is deactivated, although it does not seem to affect the thread sanitizer.
• the PR corrects also the race conditions found by the thread sanitizer tool, with minor changes in WarpX_PEC.cpp and PhysicalParticleContainer.cpp ** Done in Fix two race conditions found with thread sanitizer #4932 **
• AMReX commit is updated to f13878768ca0393be994d2fcdb834ef54b3ce254, since this fixes race conditions observed in WarpX (see Skip empty particle tiles in operator++ to avoid race condition in constructor. AMReX-Codes/amrex#3951)
• A fix proposed by @WeiqunZhang in Skip empty particle tiles in operator++ to avoid race condition in constructor. AMReX-Codes/amrex#3951 is implemented to fix a race condition in ParticleBoundaryBuffer.cpp

The thread sanitizer test uses libarcher, which should theoretically avoid false positives with OpenMP (see https://github.com/llvm/llvm-project/tree/main/openmp/tools/archer)

Some additional comments:

• export PMIX_MCA_gds=hash I am not sure why this setting is required to be honest (I am still trying to understand). However, if I run without this setting I get an error message like: The gds/shmem component attempted to attach to a shared-memory segment at a particular base address, but was given a different one, followed by a suggestion to disable the gds/shmem component. It seems to be a relatively common issue.
• export TSAN_OPTIONS='ignore_noninstrumented_modules=1' should avoid false positives with libraries not compiled with the thread sanitizer. Archer documentation suggests using this setting.
• export ARCHER_OPTIONS="verbose=1" makes WarpX print the message:
  Archer detected OpenMP application with TSan, supplying OpenMP synchronization semantics, which confirms that libarcher is in use.
• export OMPI_ALLOW_RUN_AS_ROOT=1 and export OMPI_ALLOW_RUN_AS_ROOT_CONFIRM=1 are needed because we are running the test in a docker container.

[ax3l]

Uh, is there a race condition using OpenMP threads in ParticleBoundaryBuffer::gatherParticlesFromDomainBoundaries?

[RemiLehe]

This could be related to:
#4593