Install dev dependencies with dependency groups

[mfisher87]

Move dev dependencies into dependency groups.

This is the correct way to define development dependencies that the end-user would never want to install.

See: https://peps.python.org/pep-0735/

uv will automatically install the dev group with uv sync. And the contributor could also do uv sync --all-groups to be sure they have all possible dev dependencies without needing to read the docs too closely ;)

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.

[github-actions]

👈 Launch a binder notebook on this branch for commit 2d8977c

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit 8610dda

👈 Launch a binder notebook on this branch for commit 7c56837

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

👈 Launch a binder notebook on this branch for commit 86f8b54

[chuckwondo]

Excellent! I was recently discussing with someone about the need for earthaccess to consider making deps more modular so that we can avoid pulling in deps we don't need, so this is a good first step.

I realize you're waiting to merge another PR before this one, but approving this now so you're not blocked.

[mfisher87]

Looks like the integration test failures are a result of a change in CMR holdings, not related to this PR. I'll let the tests run again now that I've done conflict resolution then merge!

[chuckwondo]

Looks like the integration test failures are a result of a change in CMR holdings, not related to this PR. I'll let the tests run again now that I've done conflict resolution then merge!

Yep, I just noticed that for another PR as well. I'm looking into the failures, but happy to have your eyes on them too!

[mfisher87]

I'm really behind on my TODO list for today but I can help look at it tomorrow or maybe the weekend!

[chuckwondo]

I'm really behind on my TODO list for today but I can help look at it tomorrow or maybe the weekend!

No worries. 2-line fix is here, if you want to approve: #1207