Improve verbose logging by logging the workspace, project, and workspace transformations

[pepicrft]

Short description 📝

I'm proposing a couple of improvements to our logging strategy:

• I removed all the debug logs in file handler. They are too level and fill the terminal with non-relevant noise like "writing file at path X".
• I added debug logs at the mappers level. This is indeed more useful because we can see the series of transformations a project, workspace, or graph goes through, and we can spot if one gets stuck or takes more time that usual.

How to test the changes locally 🧐

If you run it against a project with --verbose you should see the new logs.

Contributor checklist ✅

• The code has been linted using run mise run lint:fix
• The change is tested via unit testing or acceptance testing, or both
• The title of the PR is formulated in a way that is usable as a changelog entry
• In case the PR introduces changes that affect users, the documentation has been updated

Reviewer checklist ✅

• The code architecture and patterns are consistent with the rest of the codebase
• Reviewer has checked that, if needed, the PR includes the label changelog:added, changelog:fixed, or changelog:changed, and the title is usable as a changelog entry

[danieleformichelli]

Suggested change

	logger.debug("Transforming project \(project.name): Setting $SRCROOT to \(project.name)")
	logger.debug("Transforming project \(project.name): Setting $SRCROOT to \(project.sourceRootPath.pathString)")