Use lazy definitions for config values

[nathanjmcdougall]

No description provided.

[codspeed-hq]

CodSpeed Performance Report

Merging #504 will not alter performance

_{Comparing 500-get-performance-improvement-for-dynamic-configuration (2a13b92) with main (b7fbc12)}

Summary

✅ 1 untouched benchmarks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.49%. Comparing base (b7fbc12) to head (2a13b92).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #504   +/-   ##
=======================================
  Coverage   97.49%   97.49%           
=======================================
  Files          83       83           
  Lines        3873     3878    +5     
=======================================
+ Hits         3776     3781    +5     
  Misses         97       97           

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

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

src/usethis/_tool.py:1026

• This ConfigEntry does not provide a get_value function and will use the default _get_no_config_value, which may not be intended. Verify if lazy initialization should be applied here or if a specific get_value should be provided.

keys=["tool", "pyproject-fmt"]

src/usethis/_tool.py:743

• [nitpick] Consider refactoring repetitive inline lambda expressions that return constant values into a shared helper function to improve maintainability.

get_value=lambda: exclude_also,