Fix AIPS velocity ctype headers for correct rendering

[pford]

Reverts to previous behavior using casacore::ImageHeaderToFITS for extended file info when the AIPS velocity headers are encountered.

• What is fixed?
  Frontend issue #1771

• How does this PR solve the issue? Give a brief summary.
  CFITSIO is used to read the headers as usual. If CTYPE header value FELO-HEL or VELO-LSR is detected, the previous behavior using casacore to generate headers from the FITSImage is used so that image is rendered correctly in the frontend.

• Are there any companion PRs (frontend, protobuf)?
  No

• Is there anything else that testers should know (e.g. exactly how to reproduce the issue)?
  FITS images and screenshots are attached in frontend issue. The expected behavior described in the issue is now restored.

Checklist

• changelog updated
• e2e test passing / added corresponding fix
• no protobuf update needed
• added reviewers and assignee
• added ZenHub estimate, milestone, and release

[kswang1029]

all current e2e tests are passing. Manual tests are fine as far as I can tell. This would widen the support of FITS image cubes.

[kswang1029]

@ajm-asiaa is it possible to make an AppImage for @jehibbard to test with?

[ajm-ska]

@kswang1029 @jehibbard OK. This x86_64 Linux AppImage has been built with the pam/aips_velo_axis backend branch:

wget https://carta.asiaa.sinica.edu.tw/nightly/carta-22.09.02-72a7a1b-77afdaa6-x86_64-AppImage.tgz
tar -xvf carta-22.09.02-72a7a1b-77afdaa6-x86_64-AppImage.tgz 
./carta-22.09.02-72a7a1b-77afdaa6-x86_64.AppImage