Ignore EARTHDATA_USERNAME/PASSWORD when EARTHDATA_TOKEN is set

[chuckwondo]

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 #1121

---

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

[github-actions]

👈 Launch a binder notebook on this branch for commit 50e149d

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit 5cff7ed

👈 Launch a binder notebook on this branch for commit 5d1dc67

👈 Launch a binder notebook on this branch for commit 95d9f3b

👈 Launch a binder notebook on this branch for commit 0ebeb70

👈 Launch a binder notebook on this branch for commit 3af74a8

👈 Launch a binder notebook on this branch for commit d2af3ed

[chuckwondo]

pre-commit.ci autofix

[chuckwondo]

@betolink, @mfisher87, @jhkennedy, the integration tests seem to be regularly failing with the following, but re-running them clears things up. It seems odd that we get JSONDecodeErrors that go away on re-runs:

_____________ test_get_s3_filesystem_lowercase_location[location0] _____________
Traceback (most recent call last):
  File "/home/runner/work/***/***/.venv/lib/python3.13/site-packages/requests/models.py", line 976, in json
    return complexjson.loads(self.text, **kwargs)
           ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.13.9/x64/lib/python3.13/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ~~~~~~~~~~~~~~~~~~~~~~~^^^
  File "/opt/hostedtoolcache/Python/3.13.9/x64/lib/python3.13/json/decoder.py", line 345, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.13.9/x64/lib/python3.13/json/decoder.py", line 363, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

[betolink]

Ready to merge just noting that we may need to improve out auth unit test in the future,

[betolink]

This is a great catch, I don't like these if but we have n different ways of signing in.

[betolink]

Should we have a test that test both token and EDL credentials are present? other than that I think the code change in auth addresses the core issue.

[chuckwondo]

Thanks for the review @betolink. Yes, we'll probably want to add more tests to test various combinations of existing/non-existing env vars to cover the various cases to test for interference/precedence. I suspect that this can be covered in the context of work on the other auth issues in the backlog.