New rsyncer threads are generated incorrectly when the year rolls over during a data collection session

[tieneupin]

This is admittedly an edge case, but the usage of datetime.datetime.now().year() when constructing the destination file path for the rsync threads in Murfey led to the creation of incorrect rsync destination paths when the year rolled over from 2024 to 2025 during a Murfey data transfer session.

Additionally, with the way the rsyncinstance PostgreSQL database table was set up, it doesn't appear to be possible to reuse a previously registered rsync instance if Murfey is restarted using the same session_id.