Add support fchstat and chstat function for littlefs

[guohao15]

Summary

add functions for littlefs :

static int littlefs_fchstat(FAR const struct file *filep,
FAR const struct stat *buf, int flags);
static int littlefs_chstat(FAR struct inode *mountpt,
FAR const char *relpath,
FAR const struct stat *buf, int flags);

Impact

littlefs_vfs

Testing

NuttxSyscallTestSuites
NuttxFsTestSuites

[nuttxpr]

[Experimental Bot, please feedback here]

The provided PR description is missing some key information to determine if it meets NuttX requirements.

Here's a breakdown:

Summary:

• Insufficient: While it mentions adding functions to littlefs, it doesn't explain why this change is necessary.
  • Is it a fix for a bug?
  • Is it a new feature to improve functionality or performance?
  • What problem does it solve?
• Unclear: The description of "how the change works" is vague.
  • What do these functions specifically do?
  • How do they interact with the rest of the littlefs code?
• Missing: There's no mention of related issues. Are there any open issues this PR addresses?

Impact:

• Too Vague: Simply stating "littlefs_vfs" doesn't explain the impact.
  • Be specific about which aspects of littlefs_vfs are affected.
• Incomplete: The PR needs to address all impact points listed in the requirements. Provide "NO" or a detailed "YES" explanation for each:
  • Impact on user
  • Impact on build
  • Impact on hardware
  • Impact on documentation
  • Impact on security
  • Impact on compatibility

Testing:

• Insufficient: "NuttxSyscallTestSuites" and "NuttxFsTestSuites" are too broad.
  • List the specific test cases you ran to verify the changes.
• Missing Logs: You must provide actual testing logs (before and after the change) to demonstrate the issue and the fix.

To improve the PR:

1. Expand the Summary: Clearly articulate the "why," "what," and "how" of your changes.
2. Thoroughly Address Impact: Provide specific answers (with explanations) for each impact category.
3. Provide Detailed Testing Information:
   • Specify the exact test cases executed.
   • Include the actual "before" and "after" testing logs.

By providing this missing information, you'll make it much easier for reviewers to assess your PR and determine if it meets NuttX's standards.