JP-3729: report jwst version at end of Step.run

[braingram]

This is a second attempt at logging the jwst version at the end of pipeline/step runs. The first attempt was subject to a stpipe bug which will need to be separately addressed.

This PR wraps Step.run to log the version at the end of a run for a step that has no parent. This is similar to the previous attempt #8760 but does not use finalize_result (as that is called incorrectly by stpipe).

Testing with strun nsclean abcdefg (to make sure this works around the stpipe bug: spacetelescope/stpipe#188) gives:

2024-09-10 14:05:12,152 - stpipe - WARNING - Input dataset is not an instance of AbstractDataModel.
2024-09-10 14:05:12,152 - stpipe - INFO - PARS-NSCLEANSTEP: CRDS parameter reference retrieval disabled.
2024-09-10 14:05:12,154 - stpipe.NSCleanStep - INFO - NSCleanStep instance created.
2024-09-10 14:05:12,198 - stpipe.NSCleanStep - INFO - Step NSCleanStep running with args ('abcdefg',).
2024-09-10 14:05:12,200 - stpipe.NSCleanStep - INFO - Step NSCleanStep parameters are:
  pre_hooks: []
  post_hooks: []
  output_file: None
  output_dir: None
  output_ext: .fits
  output_use_model: False
  output_use_index: True
  save_results: True
  skip: True
  suffix: None
  search_output_file: True
  input_dir: ''
  mask_spectral_regions: True
  n_sigma: 5.0
  save_mask: False
  user_mask: None
2024-09-10 14:05:12,200 - stpipe.NSCleanStep - INFO - Step skipped.
2024-09-10 14:05:12,200 - stpipe - INFO - Results used jwst version: 1.15.2.dev237+gf252448ee

Resolves JP-3729

Tasks

• request a review from someone specific, to avoid making the maintainers review every PR
• add a build milestone, i.e. Build 11.3 (use the latest build if not sure)
• Does this PR change user-facing code / API?
  • add an entry to CHANGES.rst within the relevant release section (otherwise add the no-changelog-entry-needed label to this PR)
  • 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 60.85%. Comparing base (2aa4c18) to head (8f6814f).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #8769   +/-   ##
=======================================
  Coverage   60.84%   60.85%           
=======================================
  Files         373      373           
  Lines       38654    38657    +3     
=======================================
+ Hits        23518    23523    +5     
+ Misses      15136    15134    -2     

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

[melanieclarke]

Testing with single steps (skipped and not skipped) and with whole pipelines, it looks like this works. It is a little different from the previous implementation -- the log message comes from stpipe instead of from the step or pipeline interface, and it's printed at the end instead of next to the CRDS context message. Is that okay, @drlaw1558?

[drlaw1558]

LG2M, print location should be fine.

[melanieclarke]

Thanks for the fix!