Pre release 2.6.0

[IAlibay]

Changes made in this Pull Request:

• The usual stuff for a new release - we are in a code freeze as soon as this is done.
• Add in upper pins on NumPy so we don't have folks using 2.0 when it comes out.

PR Checklist

• CHANGELOG updated?

Developers certificate of origin

• I certify that this contribution is covered by the LGPLv2.1+ license as defined in our LICENSE and adheres to the Developer Certificate of Origin.

---

📚 Documentation preview 📚: https://mdanalysis--4241.org.readthedocs.build/en/4241/

[github-actions]

Linter Bot Results:

Hi @IAlibay! Thanks for making this PR. We linted your code and found the following:

There are currently no issues detected! 🎉

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (b21478f) 93.62% compared to head (2aa9c59) 93.62%.

Additional details and impacted files

@@            Coverage Diff             @@
##           develop    #4241     +/-   ##
==========================================
  Coverage    93.62%   93.62%             
==========================================
  Files          179      193     +14     
  Lines        24199    25304   +1105     
  Branches      4064     4064             
==========================================
+ Hits         22657    23692   +1035     
- Misses        1026     1096     +70     
  Partials       516      516             

Files Changed	Coverage Δ
package/MDAnalysis/version.py	100.00% <100.00%> (ø)

... and 14 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[IAlibay]

@MDAnalysis/coredevs can I have a quick thumbs up here?

see here for tthe relevant step in the release process: https://userguide.mdanalysis.org/dev/preparing_releases_and_hotfixes.html#getting-the-develop-branch-ready-for-a-release

[orbeckst]

lgtm 🚀

[RMeli]

LGTM, but I guess the list of relevant files to be changed in the User Guide needs to be updated?

[IAlibay]

LGTM, but I guess the list of relevant files to be changed in the User Guide needs to be updated?

Ah thanks for pointing it out, looks like I deleted the meta.yaml a couple of PRs back. I'll open a PR there.