feat(server): add path to metadata logging

[etnoy]

This PR adds path information to most log statements made by the metadata service. This makes it easier to see which files have broken metadata, especially with external libraries.

Example:

[Microservices:MetadataService] No timezone information found for asset 1072ebc8-8121-4d43-beed-508473cbd2c4: /data/import/bilder/2021/2021-06/2021-06-17/Original/20210617-064140--IMG_0542.PNG
[Microservices:MetadataService] Date and time is 2021-11-12T10:52:29+01:00 for asset 7b61ee91-2847-4ac8-a28c-2667003d10fa: /data/import/bilder/2021/2021-11/2021-11-12/Original/20211112-105229-SM-G973F-20211112_105229.JPG
[Microservices:MetadataService] Found timezone UTC+1 via OffsetTime for asset 7b61ee91-2847-4ac8-a28c-2667003d10fa: /data/import/bilder/2021/2021-11/2021-11-12/Original/20211112-105229-SM-G973F-20211112_105229.JPG
[Microservices:MetadataService] Found local date time 2021-11-12T10:52:29.000Z for asset 7b61ee91-2847-4ac8-a28c-2667003d10fa: /data/import/bilder/2021/2021-11/2021-11-12/Original/20211112-105229-SM-G973F-20211112_105229.JPG

I've also reworked and clarified some log statements

[danieldietzler]

I disagree. With an id they can quickly go to /photos/:id and check the asset out. With the path they'd need to dig in the folder structure, which is especially annoying if you're not using the storage template or an external library.

[mmomjian]

I personally would prefer that we log both? It’s a lot easier to work with the database or view the asset on the web view using the ID

[etnoy]

Fair points. I first thought of logging path for external assets and id for others, but I didn't want to make exceptions like that. I'll let you guys decide what to do here

[mertalev]

I prefer logging the ID and don't think we need to log the original path as well, which is quite verbose.

[alextran1502]

I am fine with logging both id and path for the sake of traceability

[etnoy]

I am fine with logging both id and path for the sake of traceability

I've updated the PR with your suggestion, please see the original PR description for an example