Improve debug printing for resolving origin of config settings

[chan-vince]

Summary

When running ruff in verbose mode with -v, the first debug logs show where the config settings are taken from. For example:

❯ ruff check ./some_file.py -v
[2023-11-17][00:16:25][ruff_cli::resolve][DEBUG] Using pyproject.toml (parent) at /Users/vince/demo/ruff.toml

This threw me off for a second because I knew I had no python project there, and therefore no pyproject.toml file. Then I realised it was actually reading a ruff.toml file (obvious when you read the whole print I suppose) and that the pyproject.toml is a hardcoded string in the debug log.

I think it would be nice to tweak the wording slightly so it is clear that the settings don't neccessarily have to come from a pyproject.toml file.

Test Plan

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[charliermarsh]

Thank you!