use CRDS contexts workflow

[zacharyburnett]

move back to the centralized CRDS reusable workflow for retrieving contexts; we'll need to adapt the calls in tests.yml to use jwst-edit as well

Tasks

• If you have a specific reviewer in mind, tag them.
• add a build milestone, i.e. Build 12.0 (use the latest build if not sure)
• Does this PR 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 changelog readme for instructions)
  • update or add relevant tests
  • update relevant docstrings and / or docs/ page
  • start a regression test and include a link to the running job (click here for instructions)
    • Do truth files need to be updated ("okified")?
      • after the reviewer has approved these changes, run okify_regtests to update the truth files
• if a JIRA ticket exists, make sure it is resolved properly

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.77%. Comparing base (61bd2fe) to head (0222363).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9998   +/-   ##
=======================================
  Coverage   85.77%   85.77%           
=======================================
  Files         372      372           
  Lines       40052    40052           
=======================================
  Hits        34353    34353           
  Misses       5699     5699           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pllim]

Should pin to hash?

[melanieclarke]

@zacharyburnett - what's the status of this PR?

[zacharyburnett]

@zacharyburnett - what's the status of this PR?

I'm working on simplifying the CRDS reusable workflow into an action we can use in a step, but in the meantime we should also be pinning to a specific commit hash so that changes to crds@main don't affect downstream CI; I'll work on this today

[zacharyburnett]

after talking with @braingram we've decided to move this to a more maintainable version in the upcoming package template, so we'll leave this as-is until then