gthread-posix: Do not do unguarded and non-atomic assignment of an atomic
We ended up always skipping showing the scheduler settings errors after the first call, while we were already setting such variable atomically in case it needed to.
Related to: #1672