Fix #2335, generalize update header parameter

[jphickey]

Checklist (Please check before submitting)

• 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
Expand the "Increment Sequence" boolean on transmit message functions to be a more general "Update Header" boolean, so it can be used for other fields like timestamps, checksums, or user-defined fields too.

Fixes #2335
Fixes #1157

Testing performed
Build and run CFE, sanity check, confirm headers are as expected

Expected behavior changes
Headers will be updated more consistently/generically.

Note -- Messages classified as Commands will have headers updated, too - specifically the sequence count and checksum. This will apply to messages being created by SCH/SCH_LAB, and the time signals sent by CFE TIME. Previously the sequence counter was not set in any of these messages, so it would have always been zero. Hence receivers would not be relying on it for anything, and thus setting it nonzero shouldn't break anything, either. But there is a slight chance that some code had a dependency on this always being zero.

System(s) tested on
Debian

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

[github-advanced-security]

CodeQL found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.