Disable nightly dandi read workflow for now

[rly]

Motivation

We recently added a github action to read a random set of nwb files from dandi. This always fails, usually after running for 2+ hours. The errors are almost always curl errors from using the ROS3 driver. This is not very informative until we have the bandwidth to use fsspec or remfile instead. I suggest we disable this workflow for now so that we don't waste compute cycles and I stop getting workflow failure emails.

Also Yarik raised a good point that stochastic testing is not ideal - you might miss a bug simply due to bad luck. We should test systematically instead of randomly, e.g., scan through dandisets 000001-000100 on monday, 000101-000200 on tuesday, etc.

How to test the behavior?

Show how to reproduce the new behavior (can be a bug fix or a new feature)

Checklist

• Did you update CHANGELOG.md with your changes?
• Have you checked our Contributing document?
• Have you ensured the PR clearly describes the problem and the solution?
• Is your contribution compliant with our coding style? This can be checked running flake8 from the source directory.
• Have you checked to ensure that there aren't other open Pull Requests for the same change?
• Have you included the relevant issue number using "Fix #XXX" notation where XXX is the issue number? By including "Fix #XXX" you allow GitHub to close issue #XXX when the PR is merged.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (60ec8fe) 91.99% compared to head (a3a64a8) 83.68%.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1794      +/-   ##
==========================================
- Coverage   91.99%   83.68%   -8.32%     
==========================================
  Files          27       27              
  Lines        2623     2623              
  Branches      685      685              
==========================================
- Hits         2413     2195     -218     
- Misses        138      344     +206     
- Partials       72       84      +12     

Flag	Coverage Δ
integration	?
unit	83.68% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[oruebel]

I would create an issue for future reference and add a comment in the yaml file stating why the workflow is disabled, just to leave breadcrumbs for ourselves