Enable Pylint check for LF line endings

[Urvity03]

Fixes #5315

Changes made in this Pull Request:

• Updated package/.pylintrc to set expected-line-ending-format=LF under [FORMAT].
• Added unexpected-line-ending-format to enable= under [MESSAGES CONTROL].
• Verified that Pylint reports unexpected-line-ending-format for files containing CRLF line endings.

LLM / AI generated code disclosure

LLMs or other AI-powered tools (beyond simple IDE use cases) were used in this contribution: yes

AI assistance was used to understand the repository structure, evaluate implementation options, review the relevant Pylint configuration and documentation, and assist in drafting explanations and the pull request description.

I reviewed the proposed approach, implemented the configuration changes, verified the behavior locally, committed the changes, and submitted this pull request.

PR Checklist

• Issue raised/referenced?
• Tests updated/added?
• Documentation updated/added?
• package/CHANGELOG file updated?
• Is your name in package/AUTHORS? (If it is not, add it!)
• LLM/AI disclosure was updated.

Developers Certificate of Origin

I certify that I can submit this code contribution as described in the Developer Certificate of Origin, under the MDAnalysis LICENSE.

[read-the-docs-community]

Documentation build overview

📚 MDAnalysis | 🛠️ Build #33711126 | 📁 Comparing 9105f04 against latest (0803d88)

  🔍 Preview build  

3 files changed

± index.html
± documentation_pages/analysis/wbridge_analysis.html
± documentation_pages/coordinates/XDR.html

[orbeckst]

Thank you for your contribution. However, we require our standard PR header, which includes a number of attestations, including a statement on AI use.

Please restore the standard PR header and fill that one in. We will not review PRs that do not follow our standard PULL_REQUEST_TEMPLATE.

[Urvity03]

Thank you for your contribution. However, we require our standard PR header, which includes a number of attestations, including a statement on AI use.

Please restore the standard PR header and fill that one in. We will not review PRs that do not follow our standard PULL_REQUEST_TEMPLATE.

Thanks for the feedback! I've updated the PR to use the project's standard pull request template, completed the required AI disclosure, and added my name to package/AUTHORS as requested by the template. Please let me know if there's anything else I should update.