Update node to latest LTS (v22) and other (required) dependency updates

[timvahlbrock]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/steilerDev/icloud-photos-sync/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe: Normally dependencies update would be better performed isolated, but all of the updates performed were necessary to get the tests running on node 22. ts-node wasn't working despite update, instead of fiddling around it was replaced with tsx, which is less cumbersome to use.

What is the current behavior?

Issue Number: #608

What is the new behavior?

Node 22, other updated dependencies

Does this PR introduce a breaking change?

• Yes
• No

Other information

[steilerDev]

Thanks for the contribution @timvahlbrock - unfortunately tests are still not completing fully - not sure why though :/

[steilerDev]

We urgently need to update the dependencies (but it's such a huge tedious task :D )

After that we can include your other fix as well as a fix to my inability to run the tool.

Appreciate you kicking me in the but with your contributions - keep 'em going!

[timvahlbrock]

unfortunately tests are still not completing fully - not sure why though :/

Okay, will take a look at that.

We urgently need to update the dependencies (but it's such a huge tedious task :D )

Yeah, I saw there are quite a few dependabot PRs and some dependencies like node haven't been updated in quite some time. But I get that keeping an existing project up to date gets somewhat tedious and is less exiting than diving into something new. Maybe one could introduce some more automation into dependency management? Dependabot is setup already and this projects seems to have a lot of reliable tests. I haven't seen any integration tests (or e2e, what I mean is 'covering a whole feature/use case') though, which are probably necessary to merge most dependabot PRs automatically.

After that we can include your other fix as well as a fix to my inability to run the tool.

Yay!

Appreciate you kicking me in the but with your contributions - keep 'em going!

Will do. Got some more ideas on my mind already 😉

[timvahlbrock]

Test that I just fixed failed because mock-fs seems to expect symlink paths to be abosulte now, but it was relative. Maybe this applies to the other tests as well.

[timvahlbrock]

Mock-fs documentation documents otherwise, so maybe this isn't even a breaking change but a bug that might also occur for other reasons. Might need some more investigation.

[timvahlbrock]

Reproduced and reported this issue: tschaub/mock-fs#414

[steilerDev]

am I seeing this right, all checks have passed - nice! let's get this into nightly 🙏