Autonicer

- Fixed vulnerabilites with cryptography dep (CVE-2023-0286 and CVE-2023-23931)

- Added in multi-threaded compression/decompression of files (should speed up runtime)
- Re-added in compression of non barycenter corrected mpu7_cl.evt files if a barycenter corrrected cl.evt file is created
- Fixed bug with an unexpected `Target: ` prompt appearing if OBJECT metadata cannot be found
- Fixed bug with auto-detection of barycenter correction parsing

- Fixed error handling messages for missing metadata in cl.evt files
- Switched the pull of required metadata from hdu 0 (primary header) to hdu 1 (event header) for the cl.evt NICER files
- Added OBSID corolation for easier identification

- Migrated sp.run("ls STUFF") commands to glob
- Limited get_caldb_ver() pulls to once per run of autonicer rather than once per OBSID passed in
- Added error handling for datasets lacking the required metadata
- Added unix like passthrough to `--inlist` so use cases like `--inlist *` will pass in all datasets for the current working dir

- Fixed vulnerability with CVE-2022-2341
- Fixed issue where --checkcal kills --inlist cmd

- Added `--checkcal` CLI option to check if calibrations are up to date with an existing NICER OBSID dataset
- Added `--reprocess` CLI option to reprocess an existing NICER OBSID dataset with nicerl2
- Added `--bc` CLI option to toggle the barycenter correction setting with autonicer whether pulling and reducing or reprocessing
- Added `--compress` CLI option to toggle the compression of ufa .evt files again whether pulling and reducing or just reducing
- Added `--inlist` CLI option that accepts the path to a file in csv format with the column `Input` containing the paths to NICER OBSID datasets or mpu7_cl.evt files (This works great with the output log csv files)
- Changed compression from .tar.gz format to just .gz format (decompression of .tar.gz's supported to handle files compressed with pervious versions)
- Tested issues with Astropy v5.1, Astroquery, and HEASARC. Found no issues and supressed warnings.
- Significant additions to testing taking coverage >= 90%
- Resolved dependency vulnerability with CVE-2022-42969