Fix parameter mark precedence

[ace2016]

Closes #10406.

Summary

Parameter-set marks should be more specific than marks applied to the test function, class, or module.

This change:

• makes iter_markers() yield callspec/parameter-set marks before function-level marks;
• preserves the existing own_markers storage order for compatibility;
• applies filterwarnings marks from farthest to closest so the most specific filter wins;
• preserves documented ordering between filters defined at the same level;
• adds regression tests and a changelog entry.

Root cause

Function.own_markers stores function marks before callspec marks, causing iter_markers() to report the function mark as more specific.

Additionally, warnings.filterwarnings() inserts filters at the front. Processing closest marks first therefore allowed farther class or module filters to override them. In some function-level cases, these two ordering errors accidentally cancelled each other.

Testing

• testing/test_mark.py and testing/test_warnings.py: 164 passed, 4 skipped, 1 xfailed
• testing/test_nodes.py and testing/python: 660 passed, 6 skipped, 3 xfailed
• Ruff, formatting, mypy, codespell, and the changed-file pre-commit checks passed
• git diff --check passed

Checklist

• Added regression tests.
• Added a changelog entry.
• Included Closes #10406.
• Credited AI assistance using a Co-authored-by commit trailer.
• Maintainers may push changes and squash when merging.

[RonnyPfannschmidt]

already working on it in #14630

[ace2016]

already working on it in #14630

I didn't know thank you for the notice