Scrub parameter documentation section of command codes

[skliper]

Is your feature request related to a problem? Please describe.
Parameter documentation for command codes not complete or always up to date

Describe the solution you'd like
Really the structure is the preferred place to document the parameters, the command code documentation is probably better off just referencing the structure. Need to confirm all the information in the command code documentation is in the structure documentation and then clean.

Describe alternatives you've considered
None

Additional context
Code review

Requester Info
Jacob Hageman - NASA/GSFC

[jphickey]

As part of scrubbing command docs in #1396 I also reviewed the documentation on the structures themselves.

In short - I don't see any major issues here.

In some cases structures are re-used between commands, and the structure documentation is therefore more generic in nature, where the command documentation gets into specifics about how its used. For instance EVS has a generic command that accepts a bitmask, and the CFE_EVS_BitMaskCmd_Payload_t just defines it as follows:

cFE/modules/evs/fsw/inc/cfe_evs_msg.h

Line 1020 in 33a4f19

uint8 BitMask; /**< \brief BitMask to use in the command */

However in the command documentation it says how the specific bits are defined for that particular command.

cFE/modules/evs/fsw/inc/cfe_evs_msg.h

Lines 540 to 544 in 33a4f19

	** The following bit positions apply to structure member named 'BitMask'.
	** Bit 0 - Port 1
	** Bit 1 - Port 2
	** Bit 2 - Port 3
	** Bit 3 - Port 4

So in my opinion this is appropriate - I don't see anything I feel compelled to change here.

[jphickey]

The PR for related issue #1396 also updates the description/verification sections where they were lacking, so it can be associated with this issue too (discussed in CCB 2021-07-28).