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

[matthewfeickert]

PR Summary

• Use --pytest-test-first option over --django for name-test-tests for greater clarity of convention. While this commit is somewhat trivial (there is no change in functionality) I personally think that as a developer having pytest in the option name makes more sense as it is enforcing the pytest default style of naming convention (and matplotlib doesn't use Django).
• Amends PR DEV: Add name-tests-test to pre-commit hooks #23213
  • I didn't see that this was updated in name-test-tests: add --pytest-test-first convention pre-commit/pre-commit-hooks#779 for pre-commit/pre-commit-hooks v4.3.0 when I made PR DEV: Add name-tests-test to pre-commit hooks #23213 otherwise I would have just applied it then. Sorry about that.

For further reference see:

• ci: Use '--pytest-test-first' option for naming clarity scikit-hep/pyhf#1892
• feat: Add 'name-tests-test' to pre-commit hooks example scikit-hep/scikit-hep.github.io#231

PR Checklist

Tests and Styling

• [N/A] Has pytest style unit tests (and pytest passes).
• Is Flake 8 compliant (install flake8-docstrings and run flake8 --docstring-convention=all).

Documentation

• [N/A] New features are documented, with examples if plot related.
• [N/A] New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
• [N/A] API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).
• [N/A] Documentation is sphinx and numpydoc compliant (the docs should build without error).

[tacaswell]

This only affects the pre-commit config and those test have already passed. Merging on a single review.