rename requirements-txt and requirements-txt-dev

[fpgmaas]

Rename requirements-txt and requirements-txt-dev to requirements-file and requirements-file-dev

PR Checklist

• A description of the changes is added to the description of this PR.
• If there is a related issue, make sure it is linked to this PR.
• If you've fixed a bug or added code that should be tested, add tests!
• Documentation in docs is updated

Description of changes

This PR proposes to rename requirements-txt and requirements-txt-dev to requirements-files and requirements-files-dev. If users still use the old parameters, they will be shown a deprecation warning:

Warning: In an upcoming release, support for the --requirements-txt command-line option and the requirements_txt configuration parameter will be discontinued. Instead, use --requirements-files or requirements_files under the [tool.deptry] section in pyproject.toml.

[codecov]

Codecov Report

Attention: Patch coverage is 96.29630% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 91.3%. Comparing base (e5ca1a7) to head (d9de39c).

Files	Patch %	Lines
python/deptry/core.py	75.0%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #609     +/-   ##
=======================================
+ Coverage   90.7%   91.3%   +0.5%     
=======================================
  Files         33      34      +1     
  Lines        986     996     +10     
  Branches     198     202      +4     
=======================================
+ Hits         895     910     +15     
+ Misses        74      69      -5     
  Partials      17      17             

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

[mkniewallner]

A few nit comments, but this mostly looks good to me. Just wondering if we should not name the parameters requirements-files and requirements-files-dev since they are lists.

[fpgmaas]

A few nit comments, but this mostly looks good to me. Just wondering if we should not name the parameters requirements-files and requirements-files-dev since they are lists.

Good idea. I was doubting about this a bit, since deptry . --requirements-files requirements.txt feels less intuitive than deptry . --requirements-file requirements.txt, and most projects likely have a single requirements file. But on the other hand, it is correct since it accepts a list. So let's change it to plural.