=act #15488 add @volatile on logLevel

This PR fixes the memory visibility issue introduced in #15488.

Summary:
* made `logLevel` @volatile
* Perf benchmark and results are attached.

Related:
* Also benched replacing the guard with an read-write guard, but seemed to have the opposite effect as expected actually... ( https://github.com/akka/akka/commit/5eba9fceef884b16c8764a78d0d8bb274dfbc830#diff-47ea75a55aa7f26d9b488bfb764f9d79R32 ), did not dig deeper into it for now.

Please review @viktorklang
Yeah, got it - but now thinking, does this actually break (when the write outside) memory-model wise? I don't really see how it would. Or just because "we have the lock already, so use it" wise?