fix: correct volatile description for AQS state variable (issue #2516) (#2829)

The previous description only mentioned thread visibility as the reason for
using volatile to modify the state variable. However, volatile's more important
role here is preventing instruction reordering through the happens-before rule
(volatile write happens-before subsequent read), which ensures the correctness
of lock semantics.

Fixes #2516