…y do not expire (Blacksmoke16)This PR was squashed before being merged into the 4.4 branch.Discussion----------[Cache] Set mtime of cache files 1 year into future if they do not expire| Q             | A| ------------- | ---| Branch?       | 4.4| Bug fix?      | yes| New feature?  |no| Deprecations? | no| Tickets       | -| License       | MIT| Doc PR        | -#26127 made is so that `0` is used to represent cache files that do not expire. However this was causing `touch` to be called with `0`, which was setting the create/modification time of the file to start of epoch time, which doesn't really make sense. It can cause some issues with `tar` for example as when timezones are taken into consideration you end up with warnings like:> tar: app/cache/prod/annotations/@/+/3/cdcAWwqaPORAi0TfsO5Q: implausibly old time stamp 1969-12-31 19:00:00Given the expiration of the files is stored within the file itself, it's probably safe to not `touch` it if that value is `0`. However is there actually a reason to touch it at all as a file that expires in 6 hours would show as created 6 hours into the future.I also wasn't sure how to test this, so open to suggestions on that/if we need the `touch` at all.Commits-------57cad6f [Cache] Set mtime of cache files 1 year into future if they do not expire