Refactor montepy.errors -> montepy.exceptions

[tjlaboss]

Pull Request Checklist for MontePy

Description

• Rename montepy/errors.py to montepy/exceptions.py.
• Refactor all uses accordingly throughout the codebase and test suite.
• Create a new montepy/errors.py that issues a DeprecationWarning every time montepy.errors.something is used.

Closes #764

---

General Checklist

• I have performed a self-review of my own code.
• The code follows the standards outlined in the development documentation.
• I have formatted my code with black version 25.
• I have added tests that prove my fix is effective or that my feature works (if applicable).

---

Additional Notes for Reviewers

Ensure that:

• The submitted code is consistent with the merge checklist outlined here.
• The PR covers all relevant aspects according to the development guidelines.
• 100% coverage of the patch is achieved, or justification for a variance is given.

Discussion

I think that the warning should be raised for any montepy.errors.SomeException and not at the module level.

The alternative way to deprecate was to make the warning module-level. I did it this way because either:

• we import montepy.errors in __init__.py and get the warning there, or
• we don't and montepy.errors.SomeException will be broken

The warning in __init__.py cannot be silenced with with warnings.catch_warnings(...), or else it will be caught everywhere because of how Python imports work. Doing it only at the module level would not raise a warning if a user specifically does import montepy.errors or from montepy.errors import.

---

📚 Documentation preview 📚: https://montepy--778.org.readthedocs.build/en/778/

[MicahGale]

You make a good argument for using an IDE.

[MicahGale]

Also you have missing coverage in montepy.exceptions, but coveralls is having issue and I can't find the lines that are missing.

[MicahGale]

The changelog needs adjusting. I think the missed patch coverage is my fault, and it's just showing up for you due to the rename.

[MicahGale]

I like how this page is present, but not easy to get to: https://montepy--778.org.readthedocs.build/en/778/api/montepy.errors.html

Should we exclude it via robots.txt? I think probably not. New crawlers won't find it, and it would be better if a search engine can see that it is deprecated rather than showing users a very old cached version in the search engine

[tjlaboss]

Today I learned about the :orphan: tag, which prevents the orphan warning.

[MicahGale]

Lgtm.