JP-3729: log version and crds context at end of step/pipeline runs

[braingram]

This PR adds log messages (info level) for the jwst version and crds context at the end of pipeline/step runs (by making logging calls during finalize_result). The crds context was previously logged only if reference files were used and is now logged for every run. An example of the log messages is as follows:

2024-09-06 13:13:55,491 - stpipe.Image3Pipeline - INFO - Results used CRDS context: jwst_1276.pmap
2024-09-06 13:13:55,491 - stpipe.Image3Pipeline - INFO - Results used jwst version: 1.14.1.dev350+g8efc26fdb
2024-09-06 13:13:55,491 - stpipe.Image3Pipeline - INFO - Step Image3Pipeline done

Resolves JP-3729

Closes #8749

Checklist for PR authors (skip items if you don't have permissions or they are not applicable)

• added entry in CHANGES.rst within the relevant release section
• updated or added relevant tests
• updated relevant documentation
• added relevant milestone
• added relevant label(s)
• ran regression tests, post a link to the Jenkins job below.
  How to run regression tests on a PR
• All comments are resolved
• Make sure the JIRA ticket is resolved properly

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.83%. Comparing base (d4c2f1b) to head (e16c058).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #8760   +/-   ##
=======================================
  Coverage   60.83%   60.83%           
=======================================
  Files         373      373           
  Lines       38636    38636           
=======================================
  Hits        23503    23503           
  Misses      15133    15133           

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

[drlaw1558]

LG2M in general; I can now see both the CRDS and cal pipeline version in det1, spec2, and spec3 logs.

The jwst version printed looks unexpected though. Testing this PR I get 1.14.1.dev396+gf252448ee which seems unexpected since development has moved on past 1.15.1

Indeed, even using a standalone environment with jwst 1.15.1 installed, I till get 1.14.1.dev396+gf252448ee reported by the 1.15.1 environment call to jwst.version

Are there some unresolved issues with the version call?

[braingram]

LG2M in general; I can now see both the CRDS and cal pipeline version in det1, spec2, and spec3 logs.

The jwst version printed looks unexpected though. Testing this PR I get 1.14.1.dev396+gf252448ee which seems unexpected since development has moved on past 1.15.1

Indeed, even using a standalone environment with jwst 1.15.1 installed, I till get 1.14.1.dev396+gf252448ee reported by the 1.15.1 environment call to jwst.version

Are there some unresolved issues with the version call?

Thanks for giving this a test. The version was 1.14.1.etc due to the out-of-date tags. I just pushed the updated tags (from the spacetelescope upstream) to my fork. Any local testing will also require pulling new tags to get an updated version (as the version is dynamically set from the git tag).

[braingram]

Regression tests: https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/1693/
Show same failing tests as main: https://plwishmaster.stsci.edu:8081/job/RT/job/JWST/3022/