Sort __all__ in Python modules

[bouweandela]

Description

Fix a formatting issue introduced in #2911.

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🛠 This pull request has a descriptive title and labels
• 🛠 Code is written according to the code quality guidelines
• 🛠 All checks below this pull request were successful

---

To help with the number pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[bouweandela]

The tests are failing because the server with zarr files used for testing is not available. @valeriupredoi Any idea what's going on there? Could we make the tests more robust to an offline server?

[valeriupredoi]

The tests are failing because the server with zarr files used for testing is not available. @valeriupredoi Any idea what's going on there? Could we make the tests more robust to an offline server?

temporarily unavailable - https://uor-aces-o.s3-ext.jc.rl.ac.uk/esmvaltool-zarr/pr_Amon_CNRM-ESM2-1_02Kpd-11_r1i1p2f2_gr_200601-220112.zarr3/zarr.json works well now - we could make them server-proof, but that resource is pretty much like an ESGF node, very rarely goes offline, problem is that, unlike an ESGF node that can be replaced with another node, that's the only resource

[valeriupredoi]

WTH is going on with the blithering bucket? Hang on, I spoke too soon 🤦‍♂️

EDIT: clear issue with the S3 object store at CEDA, so I pinged them:
"""
hi folks, is the S3 object store gone fishing? mc ls https://uor-aces-o.s3-ext.jc.rl.ac.uk/esmvaltool-zarr is hanging, and our nightly tests show a 503 trying to read any of the Zarr files in there? Note that mc ls-ing the top level does indeed show the various buckets in there, but accessing any bucket just hangs. Many thanks
"""
@bouweandela since no other tests fail here, and the Zarr store tests did indeed pass on Friday, I say go for the merge 🍺

[bouweandela]

we could make them server-proof

It would be great if you could have a go, this isn't the first time tests are failing because it's offline.

[valeriupredoi]

we could make them server-proof

It would be great if you could have a go, this isn't the first time tests are failing because it's offline.

shall do!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.57%. Comparing base (b8c10a8) to head (778c2f6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2914   +/-   ##
=======================================
  Coverage   95.57%   95.57%           
=======================================
  Files         266      266           
  Lines       15520    15520           
=======================================
  Hits        14834    14834           
  Misses        686      686           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[valeriupredoi]

should be fixed now, I got in touch with CEDA.

The thing about that S3 bucket is, we could pop a pytest.mark.skipif with some conditional (whuich is not quite easy to figure out), but actually - I kinda need those tests to fail so I can find out there is something wrong with the object store - at the moment, I am pretty much the only one using it, and if I don't get alerted that storage is broken, then it may well stay that way for a fair bit of time; as it was the case now, I alerted CEDA and they fixed the issue. Perhaps they should have such tests themselves, but until then, I'd prefer it fails, what do you think?

[bouweandela]

I agree that it's a good idea to set up testing for that storage service if the people operating it do not monitor it, but those should be separate tests outside of the ESMValCore repository, because now it is hampering our development.