fix dkist downstream test

[braingram]

The dkist downstream job is failing:
https://github.com/asdf-format/asdf/actions/runs/12910632436/job/36001118249#step:10:493

This is due to the current test configuration being incompatible with the ignores in the dkist pytest.ini configuration file (the tests are run in ./dkist but the configuration assumes the tests are run in ./).

This PR updates the dkist downstream CI to be compatible with the dkist pytest configuration.

Tasks

• run pre-commit on your machine
• run pytest on your machine
• Does this PR add new features and / or change user-facing code / API? (if not, label with no-changelog-entry-needed)
  • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see below for change types)
  • update relevant docstrings and / or docs/ page
  • for any new features, add unit tests

news fragment change types...

• changes/<PR#>.feature.rst: new feature
• changes/<PR#>.bugfix.rst: bug fix
• changes/<PR#>.doc.rst: documentation change
• changes/<PR#>.removal.rst: deprecation or removal of public API
• changes/<PR#>.general.rst: infrastructure or miscellaneous change

[Cadair]

I don't think it's pyargs, we skip that folder in our pytest config? https://github.com/DKISTDC/dkist/blob/main/pytest.ini#L16

[braingram]

I don't think it's pyargs, we skip that folder in our pytest config? https://github.com/DKISTDC/dkist/blob/main/pytest.ini#L16

Weird. pytest finds that config file and just seems to ignore the ignore:
https://github.com/asdf-format/asdf/actions/runs/12910632436/job/36001118249#step:10:488

[braingram]

I don't think it's pyargs, we skip that folder in our pytest config? https://github.com/DKISTDC/dkist/blob/main/pytest.ini#L16

I'm not sure why pytest isn't considering norecursedir to be relative to the pytest.ini but changing the downstream tests to run from the root of the dkist clone seems to fix the issue. Thanks @Cadair for the tip about the ignore being in pytest.ini.