Testing Valueless PVL Keyword Issues

[acpaquette]

Description

Account for valueless PVL keywords that are not reserved keywords. This change is to test how much of ISIS breaks when we account for valueless PVL keywords

Related Issue

#5566

How Has This Been Validated?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation change (update to the documentation; no code change)
• Breaking change (fix or feature that would cause existing functionality to change)
• Infrastructure change (changes to things like CI or the build system that do not impact users)

Checklist:

• I have read and agree to abide by the Code of Conduct
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and I have updated the documentation accordingly.
• I have added tests to cover my changes.
• I have added myself to the .zenodo.json document.
• I have added my user impacting change to the CHANGELOG.md document.

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

• I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[acpaquette]

All possible tests are passing on this PR. Other tests would need to have something in the data area or test data area updated. Here are the following tests that will have some data element updated:

411 - csv2table_app_test_Label (Failed)
487 - footprintmerge_app_test_360Boundary (Failed)
488 - footprintmerge_app_test_default (Failed)
577 - isisminer_app_test_pdstableformat (Failed)
582 - isisminer_app_test_stereopair (Failed)
583 - isisminer_app_test_stereopair2 (Failed)
1046 - hicalbeta_app_test_default (Failed)
1047 - hicalbeta_app_test_dnpermicrosecs (Failed)
1048 - hicalbeta_app_test_dns (Failed)
1049 - hicalproc_app_test_default (Failed)
1050 - hicalproc_app_test_destripe (Failed)
1051 - hicalproc_app_test_furrows (Failed)
1888 - HicalTest.Default (Failed)
1889 - HicalTest.Dns (Failed)
1890 - HicalTest.DnsPerMicrosecond (Failed)

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.

[github-actions]

The build and test suite have started for your pull request. View build logs for results.