CKL metadata should be have input validation and consequently disable functionality or throw errors

[Amndeep7]

Definition of done:

HDF Converters section:

• The underlying mapper should validate the checklist metadata that it receives and throw an error if it fails there. If you write the validation function well enough there, you might be able to import it and use it in Heimdall as well.

Heimdall section:
There is no validation for the checklist export modal despite us knowing the types and format of the data that should be in each field. We should do user input validation before allowing the user to export a checklist file that might not be valid and therefore fail when someone attempts to consume it.

• Each field has validation on it to at minimum require that it is of the correct typescript type (ex. number fields should be numbers)
• Each field has validation on it to ensure that it matches the expected format of that field, ex. Stigviewer should be able to open each file, and it should also make sense that something looks formatted like that.
• The export button should not be clickable unless all of the validation passes. This will probably require doing some rearchitecting of the modal to make it possible. Maybe check out Vuetify's form validation: https://v2.vuetifyjs.com/en/components/forms/

SAF CLI section:

• The SAF CLI generates CKL metadata - ensure that what the user provides meets the validation
• The SAF CLI ckl mapper integration takes in CKL metadata - ensure that the error that will propagate up from the mapper is outputted in a way that will make sense to the end user