test:add mutex socket syscall directory

[txy-21]

Summary

• Added socket, syscall, and mutex tests to testing/testsuites.
• Some test cases have been added that cover the functionality of fs, mutex, pthread, socket, and syscall.
• Code formatting fixes.

Impact

Testing / new test scenarios.

Testing

• GH CI.
• How did I perform local tests?

[cederom]

Thank you @txy-21, please update PR description it does not seem to match PR content..?

[xiaoxiang781216]

Thank you @txy-21, please update PR description it does not seem to match PR content..?

Do you need update Make.defs and CMakelist.txt? @txy-21

[cederom]

Build errors :-(

[cederom]

Lets try the build :-)

[lupyuen]

Sorry @txy-21 I think rv-virt:citest might be failing due to this PR, could you take a look? Thanks!
https://github.com/NuttX/nuttx/actions/runs/12390461445/job/34585612917#step:7:88

Configuration/Tool: rv-virt/citest
kernel/fs/cases/fs_fsync_test.c: In function 'test_nuttx_fs_fsync02':
Error: kernel/fs/cases/fs_fsync_test.c:140:20: error: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Werror=format=]
  140 |   syslog(LOG_INFO, "the fbsize = %"PRIu64",buffer size=%d\n",
      |                    ^~~~~~~~~~~~~~~~
  141 |         statfsbuf.f_bsize, bufsize);
      |         ~~~~~~~~~~~~~~~~~
      |                  |
      |                  size_t {aka unsigned int}

BTW to test rv-virt:citest locally we could use Docker:
apache/nuttx#15170

sudo docker run \
  -it \
  --name nuttx \
  ghcr.io/apache/nuttx/apache-nuttx-ci-linux:latest \
  /bin/bash
cd
git clone https://github.com/apache/nuttx
git clone https://github.com/txy-21/nuttx-apps \
  apps \
  --branch add-kernel-dir
pushd nuttx ; echo NuttX Source: https://github.com/apache/nuttx/tree/$(git rev-parse HEAD) ; popd
pushd apps  ; echo NuttX Apps: https://github.com/apache/nuttx-apps/tree/$(git rev-parse HEAD) ; popd
cd nuttx/tools/ci
./cibuild.sh -c -A -N -R testlist/risc-v-05.dat 

[cederom]

Thanks @lupyuen! Looks like fix is here #2900 just need a rebase due SPDX updates :-)