Fix scheduler cancellation/state visibility and NUMA mapping

[yunuservices]

This PR fixes several scheduler/NUMA correctness issues introduced by the scheduler refactor.

• Fix Linux NUMA CPU->node mapping assignment in LinuxNuma so mapped CPUs are always updated.
• Make SchedulableTick state visibility thread-safe (volatile) and access it via accessor.
• Enforce scheduledStart validation in EDFSchedulerThreadPool.schedule(...).

Why

• Incorrect CPU->NUMA mapping could produce wrong locality decisions.
• Unsafely published task state could cause stale reads under concurrency.
• EDF scheduling accepted tasks without start deadlines.
• EDF cancellation path defined cancel state but did not reliably apply it.
• Work-stealing score calculation could hit divide-by-zero on invalid distance values.

(I wrote text wrong, edited now.)