Update deprecated pytest hook arg

[glatterf42]

Our whole CI is failing (same for several downstream projects) because one of the pytest hooks here is using a deprecated argument: startdir has been replaced by start_path. This was kindly pointed out in pytest-dev/pytest#12061, though I have to admit even with the linked deprecation changelog, this might not have been entirely clear to me. After all, the changelog says the hook is now receiving 'additional arguments', not 'changed arguments'. Either way, this PR includes the fix.

Should we update the release notes since other projects might have seen failures due to the hook arguments being out of date? If so, we haven't received an issue yet.

How to review

• Read the diff and note that the CI checks all pass.

PR checklist

• Continuous integration checks all ✅
• [ ] Add or expand tests; coverage checks both ✅ Just an internal change
• [ ] Add, expand, or update documentation. Just an internal change
• [ ] Update release notes. Just an internal change

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.9%. Comparing base (049689a) to head (ba6d7af).

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #519   +/-   ##
=====================================
  Coverage   98.9%   98.9%           
=====================================
  Files         44      44           
  Lines       4795    4795           
=====================================
  Hits        4743    4743           
  Misses        52      52           

Files	Coverage Δ
ixmp/testing/__init__.py	95.9% <100.0%> (ø)

[khaeru]

As noted in Slack, this is ready to merge.

The Windows job failures are acceptable: they occur due to an unrelated issue with the third-party codecov/codecov-action that has also been seen in scheduled (non-PR) runs. The test suite passes, but then the coverage upload stalls, in turn stalling the overall job.

Since this issue with pytest >= 8.1 affects scheduled and PR runs downstream (e.g. iiasa/message_ix#784), we can merge and addressing that issue separately.