fix: use safe time as the default time

[merceyz]

What's the problem this PR addresses?

• The patch plugin isn't using the safe time when writing new files and creating their parent directory
• The copyPromise algorithm isn't using the safe time
• perf: convert chmod calls to mode arguments #3254 fixed a bug in ZipFS where writeFileSync didn't set the mode on files but didn't update the cache key causing checksum mismatches for patched packages where files are created (fsevents)

How did you fix it?

Moved the safe time to fslib, updated everything I could find to use it, and updated the cache version for the affected protocols

Checklist

• I have read the Contributing Guide.
• I have set the packages that need to be released for my changes to be effective.
• I will check that all automated PR checks pass before the PR gets reviewed.

[merceyz]

Comparing the archive for the patched fsevents from master with the one in this PR:

/node_modules
-atimeMs: 315532800000
+atimeMs: 456789000000
-mtimeMs: 315532800000
+mtimeMs: 456789000000
-ctimeMs: 315532800000
+ctimeMs: 456789000000
-birthtimeMs: 315532800000
+birthtimeMs: 456789000000
-atime: 1980-01-01T00:00:00.000Z
+atime: 1984-06-22T21:50:00.000Z
-mtime: 1980-01-01T00:00:00.000Z
+mtime: 1984-06-22T21:50:00.000Z
-ctime: 1980-01-01T00:00:00.000Z
+ctime: 1984-06-22T21:50:00.000Z
-birthtime: 1980-01-01T00:00:00.000Z
+birthtime: 1984-06-22T21:50:00.000Z

/node_modules/fsevents/vfs.js
-atimeMs: 315532800000
+atimeMs: 456789000000
-mtimeMs: 315532800000
+mtimeMs: 456789000000
-ctimeMs: 315532800000
+ctimeMs: 456789000000
-birthtimeMs: 315532800000
+birthtimeMs: 456789000000
-atime: 1980-01-01T00:00:00.000Z
+atime: 1984-06-22T21:50:00.000Z
-mtime: 1980-01-01T00:00:00.000Z
+mtime: 1984-06-22T21:50:00.000Z
-ctime: 1980-01-01T00:00:00.000Z
+ctime: 1984-06-22T21:50:00.000Z
-birthtime: 1980-01-01T00:00:00.000Z
+birthtime: 1984-06-22T21:50:00.000Z
-mode: 100666
+mode: 100644