Add aarch64 testing via CirrusCI

[IAlibay]

Partly towards #4054

Changes made in this Pull Request:

• osx-arm64 updates:
  • use pytest-xdist
  • switch over to ventura from monterey
  • reduced CI execution time from 9m to 3m
• aarch64 linux testing
  • 8 core, 8 GB aarch64 runner using latest python docker build
• start using starlark config for cirrus

PR Checklist

• Tests?
• Docs?
• CHANGELOG updated?
• Issue raised/referenced?

---

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

[github-actions]

Linter Bot Results:

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

Some issues were found with the formatting of your code.

Code Location	Outcome
main package	✅ Passed
testsuite	⚠️ Possible failure

Please have a look at the darker-main-code and darker-test-code steps here for more details: https://github.com/MDAnalysis/mdanalysis/actions/runs/4677222394/jobs/8284476513

---

Please note: The black linter is purely informational, you can safely ignore these outcomes if there are no flake8 failures!

[IAlibay]

9m to 3m for the cirrus osx-arm64 runner.. not bad

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (30baa14) 93.59% compared to head (a5f9faa) 93.59%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #4120   +/-   ##
========================================
  Coverage    93.59%   93.59%           
========================================
  Files          192      192           
  Lines        25134    25134           
  Branches      4056     4056           
========================================
  Hits         23524    23524           
  Misses        1092     1092           
  Partials       518      518           

see 3 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[IAlibay]

How interesting, we can now reproduce #4112

[IAlibay]

How interesting, we can now reproduce #4112

The issue is very much "because root", the question now is - how do we deal with this, either we detect root uuid in tests (flaky), or we just say "if you're running as a privileged user, don't".

[IAlibay]

Ok this should be good to review, will need this merged ahead of fully fixing #4054 for the v2.5.0 release.

[IAlibay]

CI issues seem to be related to pytest 7.3, not the changes added here (surprisly we touched the same tests at the same time, but it seems to be a coincidence). See: #4121

[IAlibay]

@MDAnalysis/coredevs this needs to be the next priority review so that we can get #4054 done in time for the 2.5 release.

[hmacdope]

Nitpick but otherwise looks good, feel free to ignore.

[hmacdope]

Link?