fix(config): ensure the actually used config file is correct, fix single config file being detected as duplicated, better test coverage

[bearomorphism]

This is an improvement a fix based on #1773

• Improved test coverage of multiple config file warning
• Ensured the consistency of actually used config file, which is not always the first element of the candidates

Closes #1787

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.96%. Comparing base (aa82b98) to head (b47ee67).
⚠️ Report is 7 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1784   +/-   ##
=======================================
  Coverage   97.95%   97.96%           
=======================================
  Files          60       60           
  Lines        2646     2648    +2     
=======================================
+ Hits         2592     2594    +2     
  Misses         54       54           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Lee-W]

In case your uv project doesn’t have a lockfile or any uv specific config, you can still force poe to use the uv executor like so:

Yep, agree this might not be necessary. No strong opinion on this one. Will leave it to @noirbizarre

[bearomorphism]

In case your uv project doesn’t have a lockfile or any uv specific config, you can still force poe to use the uv executor like so:

Yep, agree this might not be necessary. No strong opinion on this one. Will leave it to @noirbizarre

Are you replying to #1795 🤔