fix: avoid copy atomic value

[medcl]

Fix warning: Call of 'task.RegisterScheduleTask' copies the lock value: type 'task.ScheduleTask' contains 'atomic.Bool' contains 'interface{}' which is 'sync.Locker'

This warning is a result of Go’s strict handling of types containing atomic fields or synchronization primitives (e.g., sync.Locker). When such types are copied, it can cause subtle bugs because the copied value shares access to underlying synchronization mechanisms or memory.

This pull request includes changes to the core/task/task.go file to improve the handling of the isTaskRunning field in task structures. The changes ensure that isTaskRunning is properly initialized as a pointer to an atomic.Bool.

Initialization improvements:

• core/task/task.go: Added initialization of isTaskRunning as a pointer to an atomic.Bool in the registerTransientTask function.
• core/task/task.go: Changed the isTaskRunning field in the ScheduleTask struct to be a pointer to an atomic.Bool instead of a direct atomic.Bool instance.
• core/task/task.go: Added initialization of isTaskRunning as a pointer to an atomic.Bool in the RegisterScheduleTask function.

[luohoufu]

LGTM