Verification pipeline boilerplate

[delucchi-cmu]

Change Description

• My PR includes a link to the issue that I am addressing

Adds the boilerplate for running the new verification pipeline within the existing hipscat-import pipeline infrastructure.

This allows us to inherit:

• dask client creation
• success/failure email
• creation and management of output path and temporary path
• basic provenance tracking

Code Quality

• I have read the Contribution Guide
• My code follows the code style of this project
• My code builds (or compiles) cleanly without any errors or warnings
• My code contains relevant comments and necessary documentation

New Feature Checklist

• I have added or updated the docstrings associated with my feature using the NumPy docstring format

[codecov]

Codecov Report

Merging #126 (883e7d3) into main (1525da2) will not change coverage.
Report is 14 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #126   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        24    +2     
  Lines          900       939   +39     
=========================================
+ Hits           900       939   +39     

Files	Coverage Δ
src/hipscat_import/catalog/resume_plan.py	100.00% <100.00%> (ø)
src/hipscat_import/catalog/run_import.py	100.00% <100.00%> (ø)
src/hipscat_import/index/run_index.py	100.00% <100.00%> (ø)
src/hipscat_import/pipeline_resume_plan.py	100.00% <100.00%> (ø)
src/hipscat_import/soap/resume_plan.py	100.00% <100.00%> (ø)
src/hipscat_import/soap/run_soap.py	100.00% <100.00%> (ø)
src/hipscat_import/verification/arguments.py	100.00% <100.00%> (ø)
...rc/hipscat_import/verification/run_verification.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[troyraen]

I'm out of the office unexpectedly, but plan to be back this Thursday, Sept 7. I can take a closer look when I return. In the meantime, can you give me some direction about what kind of review you'd like? I gather that you'd like me to write the code that run_verification.run will execute? If so, I can look at this PR from the perspective of understanding how to do that. Are there other things you'd like me to look at?

[delucchi-cmu]

Our general guidelines and philosophy on code reviews are in this wiki entry: https://github.com/lincc-frameworks/docs/wiki/Design-and-Code-Review-Policy

I'm hoping that by getting this boilerplate PR out of the way, adding the meaningful implementation of the verification logic will be more straightforward. Your assumption of the perspective I'm looking for is correct, though I'm planning to also contribute some to the logic in run_verification - you won't be out on your own =]

[troyraen]

Some questions and comments below, but overall LGTM and I'll approve and let you decide when you're ready to merge.