ENH: Declare ruff's vendored-file excludes once in pyproject.toml

versioneer.py and monai/_version.py were excluded from ruff twice,
independently: .pre-commit-config.yaml's ruff hook via its own
"exclude:" regex, and runtests.sh via hardcoded --exclude flags on
the CLI invocation. Neither read from pyproject.toml, so a third
direct "ruff check" invocation (an editor, a one-off shell command)
would lint and offer to rewrite both files -- 200 violations today.

extend-exclude in [tool.ruff] gives runtests.sh's directory-walk
invocation (and any other caller that lets ruff discover its own
config) the same exclusion pre-commit's hook already applies, so the
CLI flags on the runtests.sh invocation are redundant and dropped.

Verified: 'ruff check' with pyproject.toml's new extend-exclude,
given the directory the way runtests.sh gives it, still reports
'All checks passed!' for the tree, and 'runtests.sh --ruff' is
unaffected end to end. Ruff ignores config exclude when handed
explicit filenames instead of a directory (the pre-commit hook path,
already governed by its own hook-level exclude, and not something
this PR touches).

Author: hjmjohnson

pyproject.toml

@@ -292,6 +292,8 @@ exclude = '''
 [tool.ruff]
 line-length = 120
 target-version = "py310"
+# .pre-commit-config.yaml's ruff hook excludes these separately at the pre-commit layer
+extend-exclude = ["versioneer.py", "monai/_version.py"]
 
 [tool.ruff.lint]
 select = [

runtests.sh

@@ -599,9 +599,9 @@ then
 
     if [ $doRuffFix = true ]
     then
-        "${PY_EXE}" -m ruff check --fix --unsafe-fixes --exclude versioneer.py --exclude "monai/_version.py" "$homedir"
+        "${PY_EXE}" -m ruff check --fix --unsafe-fixes "$homedir"
     else
-        "${PY_EXE}" -m ruff check --exclude versioneer.py --exclude "monai/_version.py" "$homedir"
+        "${PY_EXE}" -m ruff check "$homedir"
     fi
 
     ruff_status=$?