support pooch >= 1.7

[bmcfee]

Reference Issue

Fixes #1688

What does this implement/fix? Explain your changes.

This PR rewrites the example data registry file to use the new format introduced in pooch 1.7.0.

It removes the upper pin on the pooch dependency, and bumps our minimum supported version to 1.7.

Any other comments?

Per my comments in #1688, I'm still ambivalent on this, as it would force an update to user environments that is not backward-compatible. But, since it's extremely unlikely to affect anyone, I'm leaning toward rolling it into 0.10.1 anyway.

No functionality changes here, so as long as the CI passes and builds cleanly, it should be good to merge.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (519d6d9) 98.75% compared to head (63fb438) 98.75%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1727   +/-   ##
=======================================
  Coverage   98.75%   98.75%           
=======================================
  Files          34       34           
  Lines        4587     4587           
=======================================
  Hits         4530     4530           
  Misses         57       57           

Flag	Coverage Δ
unittests	98.75% <ø> (ø)

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

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

[bmcfee]

Aha... this is going to be a pain for the historical documentation build.

I'll have to rethink this...

[bmcfee]

Two ideas here:

1. (already implemented just now) is to leave the upper version pin in the docs environment. This way, old versions will continue to build with pooch 1.6, but we can still test the latest on 1.7.
2. Instead of just reformatting the registry, we can rename the files server-side to avoid apostrophes. This can be done with a few symbolic links, and old versions will continue to work fine. Doing this will allow us to have a single registry file that works with pooch 1.6 or 1.7, so the minimum version requirement can stay where it was and we don't force environment updates on users. However, we will still need the upper version pin on the doc environment.

[bmcfee]

I've updated the librosa data repo to move the offending filenames, but add backward-compatible symbolic links so that old versions continue to work. I think this ought to do the trick.