ci: Use '--pytest-test-first' option for naming clarity

[matthewfeickert]

Description

Following pre-commit/pre-commit-hooks#779 and pre-commit-hooks v4.3.0 use the --pytest-test-first option of name-tests-test for clarity.

This amends PR #1877.

Related: scikit-hep/scikit-hep.github.io#231

Checklist Before Requesting Reviewer

• Tests are passing
• "WIP" removed from the title of the pull request
• Selected an Assignee for the PR to be responsible for the log summary

Before Merging

For the PR Assignees:

• Summarize commit messages into a comprehensive review of the PR

* Update github.com/pre-commit/pre-commit-hooks: v4.2.0 → v4.3.0 to get
`--pytest-test-first` option for name-test-tests.
* Use `--pytest-test-first` option for name-test-tests for greater clarity of
convention.
* Amends PR #1877.

[codecov]

Codecov Report

Merging #1892 (474c7e3) into master (474c7e3) will not change coverage.
The diff coverage is n/a.

❗ Current head 474c7e3 differs from pull request most recent head aab274c. Consider uploading reports for the commit aab274c to get more accurate results

@@           Coverage Diff           @@
##           master    #1892   +/-   ##
=======================================
  Coverage   98.17%   98.17%           
=======================================
  Files          68       68           
  Lines        4331     4331           
  Branches      730      730           
=======================================
  Hits         4252     4252           
  Misses         46       46           
  Partials       33       33           

Flag	Coverage Δ
contrib	26.34% <0.00%> (ø)
doctest	60.63% <0.00%> (ø)
unittests-3.10	96.05% <0.00%> (ø)
unittests-3.7	96.03% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 474c7e3...aab274c. Read the comment docs.

[matthewfeickert]

As this is amending PR #1877, I'm going to approve and merge this myself given that it is already in when other maintainers were on holiday. As always, PRs approved by a single core dev can be reverted as needed by the rest of the dev team.