test: add filesystem check to test-fs-stat-date.mjs

[LiviaMedeiros]

main-based alternative to: #44129

Skip the test if filesystem doesn't provide correct atime or mtime value from fs.stat().

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/45949/

[github-actions]

Fast-track has been requested by @LiviaMedeiros. Please 👍 to approve.

[LiviaMedeiros]

Marking as fast-trackPRs that do not need to wait for 48 hours to land. in case if we need this in v16.17.0 before deadlines.

[nodejs-github-bot]

Landed in 86276d3

[targos]

@LiviaMedeiros I cherry-picked #43714 and this commit to v16.x-staging but it doesn't seem to work as expected.
See #44542 (comment)
https://ci.nodejs.org/job/node-test-binary-arm-12+/15525/RUN_SUBSET=1,label=pi2-docker/testReport/junit/(root)/test/parallel_test_fs_stat_date/

[LiviaMedeiros]

According to #44129 (comment), this test platform uses NFS mounts.
According to RFC 1813, Page 21, NFSv3 uses unsigned types for timestamps:

structnfstime3{uint32 seconds; uint32 nseconds};

While NFSv4 (RFC 7530, Page 21) uses signed:

structnfstime4{int64_t seconds; uint32_t nseconds};

This is my best guess on why could this happen.

Opened #44707 against main, let me know if backport PR would be more convenient.

[juanarbol]

@LiviaMedeiros I cherry-picked #43714 and this commit to v16.x-staging but it doesn't seem to work as expected. See #44542 (comment)https://ci.nodejs.org/job/node-test-binary-arm-12+/15525/RUN_SUBSET=1,label=pi2-docker/testReport/junit/(root)/test/parallel_test_fs_stat_date/

This is causing the CI to fail in the v16.x release branch. I will label this as dont-land-on-v16.x; feel free to remove it if needed