bump ExampleNotebooks version

[atravitz]

For now we're still manually pinning to an examplenotebooks release. We may want to transition to pointing to stable if we decide to use that release pattern.

Checklist

• All new code is appropriately documented (user-facing code must have complete docstrings).
• Added a news entry, or the changes are not user-facing.
• Ran pre-commit by making a comment with pre-commit.ci autofix before requesting review.

Manual Tests: these are slow so don't need to be run every commit, only before merging and when relevant changes are made (generally at reviewer-discretion).

• GPU integration tests
• example notebook testing
• packaging tests: run this for any large feature PRs or PRs that add test data.

Developers certificate of origin

• I certify that this contribution is covered by the MIT License here and the Developer Certificate of Origin at https://developercertificate.org/.

[github-actions]

No API break detected ✅

[mikemhenry]

LGTM -- I do think point to stable or something makes the most sense OR we setup a little version bump script OR we add this to a check list