Direct users searching for SEDAC data to new provider ESDIS

[itcarroll]

Pull Request (PR) draft checklist - click to expand

• Please review our
  contributing documentation
  before getting started.
• Populate a descriptive title. For example, instead of "Updated README.md", use a
  title such as "Add testing details to the contributor section of the README".
  Example PRs: #763
• Populate the body of the pull request with:
  • A clear description of the change you are proposing.
  • Links to any issues resolved by this PR with text in the PR description, for
    example closes #1. See
    GitHub docs - Linking a pull request to an issue.
• Update CHANGELOG.md with details about your change in a section titled
  ## Unreleased. If such a section does not exist, please create one. Follow
  Common Changelog for your additions.
  Example PRs: #763
• Update the documentation and/or the README.md with details of changes to the
  earthaccess interface, if any. Consider new environment variables, function names,
  decorators, etc.

Click the "Ready for review" button at the bottom of the "Conversation" tab in GitHub
once these requirements are fulfilled. Don't worry if you see any test failures in
GitHub at this point!

Pull Request (PR) merge checklist - click to expand

Please do your best to complete these requirements! If you need help with any of these
requirements, you can ping the @nsidc/earthaccess-support team in a comment and we
will help you out!

• Add unit tests for any new features.
• Apply formatting and linting autofixes. You can add a GitHub comment in this Pull
  Request containing "pre-commit.ci autofix" to automate this.
• Ensure all automated PR checks (seen at the bottom of the "conversation" tab) pass.
• Get at least one approving review.

Fixes #1032

After SEDAC was dismantled and the data archive taken offline, ESDIS archived the data and began distributing with provider ID "ESDIS". The PR should make this "backend" switch transparent to users.

---

📚 Documentation preview 📚: https://earthaccess--1087.org.readthedocs.build/en/1087/

[github-actions]

👈 Launch a binder notebook on this branch for commit bee8029

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit 09bbbff

👈 Launch a binder notebook on this branch for commit 47b9f20

👈 Launch a binder notebook on this branch for commit 421224a

👈 Launch a binder notebook on this branch for commit fffa768

👈 Launch a binder notebook on this branch for commit acaf935

[betolink]

If SEDAC collections are now under ESDIS what would be the S3 credentials endpoint? I only see SEDAC as an on-prem provider. @itcarroll

EDIT: I think there are no S3 endpoints for the SEDAC collections but they are hosted in AWS, and cloud_hosted=true doesn't work. I assume some weirdness from the rushed migration.

[itcarroll]

I can get more info if you think w need it, but your edit is what I also guessed based on the URLs provided by CMR. It all seems to work as if there were an on-prem provider. 🤷