JP-3225: Gaia proper motions enabled

[s-goldman]

Resolves JP-3225

This PR enables catalog positions to corrected for GAIA proper motions. The code follows the logic from romancal using an new epoch variable. The default for this variable is set to 2016.0 or no correction.

Checklist for maintainers

• 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
• Make sure the JIRA ticket is resolved properly

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (677c526) 76.62% compared to head (184ffcd) 76.62%.

❗ Current head 184ffcd differs from pull request most recent head 55fc080. Consider uploading reports for the commit 55fc080 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7614   +/-   ##
=======================================
  Coverage   76.62%   76.62%           
=======================================
  Files         456      456           
  Lines       36831    36833    +2     
=======================================
+ Hits        28221    28223    +2     
  Misses       8610     8610           

Flag	Coverage Δ		*Carryforward flag
nightly	77.43% <ø> (-0.01%)	⬇️	Carriedforward from 677c526

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files	Coverage Δ
jwst/tweakreg/astrometric_utils.py	89.39% <100.00%> (+0.33%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[nden]

It's for maintainers in general. However, it's also a reminder for those submitting PRs about what is expected. I think it's best if you check off items as you work through the PR and comments. It helps greatly the maintainer if those submitting PRs check these off and run regression tests with their PR.

[s-goldman]

https://plwishmaster.stsci.edu:8081/blue/organizations/jenkins/RT%2FJWST-Developers-Pull-Requests/detail/JWST-Developers-Pull-Requests/760/pipeline

[hbushouse]

Another regtest run started at https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/769

[hbushouse]

Another regtest run started at https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/771

[s-goldman]

https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/771

Looks like 3 regression tests failed related to small difference (~1E-5) in generated results and the truth files. I can try to investigate this, but it may take me a little longer to get up to speed. Once the difference are confirmed to be benign, I can update the truth files.

[hbushouse]

https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/771

Looks like 3 regression tests failed related to small difference (~1E-5) in generated results and the truth files. I can try to investigate this, but it may take me a little longer to get up to speed. Once the difference are confirmed to be benign, I can update the truth files.

I think the small differences showing up are likely expected due to the inclusion of proper motion. I think we can merge the PR and do a detailed investigation of the new results once it's available in jwst/master.