sched/wdog: use small lock to protect g_wdactivelist

[hujun260]

Summary

sched/wdog: use small lock to protect g_wdactivelist
reason:
We would like to replace the critical section with a small lock.

This PR requires #15129 to be merged first.

Impact

wdog

Testing

ci ostest(qemu-armv8a:nsh_smp)

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR does not fully meet the NuttX requirements. While it provides a summary and testing information, it lacks crucial details.

Here's what's missing:

• Summary: Lacks sufficient detail. How does using a small lock work? What specific code changes are made? Simply stating "replace critical section with small lock" is insufficient. What benefits does this change offer (e.g., performance, reduced interrupt latency)?
• Impact: The impact section is woefully incomplete. It only mentions "wdog" which is not helpful. All "NO/YES" questions need to be answered explicitly, and a description provided for any "YES" answers. Consider impacts like:
  • Performance: Does this change improve or degrade performance?
  • Memory usage: Does this change affect memory usage?
  • Real-time behavior: Are there any changes to real-time guarantees?
• Testing: While it mentions "ci ostest," it lacks specific details about the results of the tests. Providing "before" and "after" logs is mandatory, even if they are identical (to demonstrate no regressions). The provided logs are empty placeholders. Information about the build host (OS, compiler version) is also missing.

The PR needs substantial revision to meet the NuttX requirements. It needs to provide a more thorough explanation of the changes, a detailed impact assessment, and actual testing logs demonstrating the effect of the change.