Avoid ScheduledTask timer lock inversion

[ac1982]

Fixes #1099.

ScheduledTask#reschedule and #reset acquire the task lock before entering TimerSet. Queue comparisons acquire the timer lock before calling schedule_time, which currently takes the task lock. These opposite orders can deadlock.

Use the library's existing attr_volatile for the schedule time, following the direction discussed by @snickell and @eregon in the issue. All reads/writes use its generated accessors, and the writer stays private. This removes the task-lock acquisition from queue comparisons while preserving the library's cross-interpreter visibility mechanism.

Two latch-coordinated regressions force the conflicting lock order for reset and reschedule. Both time out on master and pass with the change; they also check that the task stays pending with its updated delay and schedule time. Update the changelog as requested by the contribution guide.

Validation on CRuby 3.3.8 / Linux arm64:

• Regression before fix: 2 examples, 2 failures; after fix: 2 examples, 0 failures.
• ScheduledTask + TimerSet specs: 113 examples, 0 failures.
• bundle exec rake (including native C-extension build): 2,802 examples, 0 failures, 16 pending.
• git diff --check passed.

JRuby, TruffleRuby, Windows, and other CRuby versions were not run locally. Optional YARD documentation tasks were unavailable because YARD was not installed. AI assistance: OpenAI Codex investigated, implemented, and ran the checks above.

[joshuay03]

Thanks!