Should File IO tasks report in logs absolute paths of items they operate on?

### Summary

Currently in most places tasks log relative paths, respectively paths that are inputted when reporting messages/warnings/errors (but not all, there is some absolute path logging in Copy task)

### Background and Motivation

https://github.com/dotnet/msbuild/pull/12914 absolutizes paths that the tasks are working with internally
we can easily report these absolute paths which may aid with debugging as customers would not need to correlate the task origin + the logged relative path, but it would be clearer from the message what happened.

### Proposed Feature

Expand the places where we log absolute path in Tasks since we compute it anyway in the task, so we can also log it.

### Alternative Designs

keep as is