Update pydata/pydata-sphinx-theme requirement to fc1ce62aa1d38fb3dc7e9cee2f191909d1196971

[dependabot]

Updates the requirements on pydata/pydata-sphinx-theme to permit the latest version.

Changelog

Sourced from pydata/pydata-sphinx-theme's changelog.

Release instructions

This page contains the steps to make a release and some helpful resources to get you started.

Create an issue and copy/paste the steps below to release a new version. Close the issue when it is done.

These steps should be taken in order to create a new release![^release-refs]

**Double check for quality-control**

 There are no open issues with a impact: block-release label
 Check wether the localization files are up-to-date, or open a PR to update them if needed.

Prepare the codebase for a new version

 Bump __version__ in __init__.py
 Update our version switcher .json file with the new version
 Make a release commit: git commit -m 'bump: 0.1.9 → 0.2.0'
 Push the RLS commit git push upstream main
 If a release candidate is needed, tick this box when we're now ready for a full release.

Make the release

 Start a new GitHub release

Call the release the current version, e.g. v0.2.0
In the Choose a Tag: dropdown, type in the release name (e.g., v0.2.0) and click "Create new tag"
In the Target: dropdown, pin it to the release commit that you've just pushed.
Generate the automatic release notes, eventually manually specify the previous version (useful when several release candidate have been made)


 Confirm that the release completed

The publish github action job has completed successfully in the actions tab.
The PyPI version is updated


 Hide the previous patch version build in the RDT interface if needed.
 Open a new PR to bump the version to the next dev target (e.g. 0.2.1.dev0) in __init__.py
 Celebrate, you're done!

[^release-refs]: Taken from the release checklist. See the release documentation for an overview of release processes.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)