Fix #126, Standardize command responses

[thnkslprpt]

Checklist

• I reviewed the Contributing Guide.
• I signed and emailed the appropriate Contributor License Agreement to GSFC-SoftwareRelease@mail.nasa.gov and copied cfs-program@lists.nasa.gov.

Describe the contribution

• Fixes Standardization of Command Responses #126
  • Adds checks if already in the commanded state (where it makes sense - for example, not for resetting the command counters or for the NOOP)
  • Issues an event string to that effect informing the user that we are already in the commanded state (but still reuses the same EID)
  • Adds 6 new tests for the new logic
  • couple of unrelated typos etc. fixed as well

Testing performed
GitHub CI actions all passing successfully (incl. Build + Run, Unit/Functional Tests etc.).
New tests added for added functionality.

Expected behavior changes
HS command responses will now align fully with expectations, and will inform the user if the software is already in the commanded state (and not set it again unnessesarily).

System(s) tested on
Debian GNU/Linux 11 (bullseye)
Current main branch of cFS bundle.

Contributor Info
Avi Weiss   @thnkslprpt

[dzbaker]

@thnkslprpt Would you be able to resolve the merge conflicts in this PR and remove the changes to the superfluous comments (in hs_verify.h)?

[thnkslprpt]

@thnkslprpt Would you be able to resolve the merge conflicts in this PR and remove the changes to the superfluous comments (in hs_verify.h)?

@dzbaker that's updated now mate.