Explicit group RTS command requirements

[skliper]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I reviewed the README file to see if the feature is in the major future work.
• I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
Start and stop RTS command requirements are written w a "compound" style, should be two separate requirements since it's two separate commands (SC4000, SC4003):

SC/docs/sc_FunctionalRequirements.csv

Lines 91 to 94 in 52fb737

	SC4000,SC4000,"Upon receipt of a Start RTS Command, SC shall execute the command-specified RTS, or range of RTS, provided all of the following conditions are met:
	a) The command-specified RTS, or range of RTS, is not currently executing
	b) The RTS, or range of RTS, table(s) is Enabled
	c) The RTS, or range of RTS, table(s) has been Loaded",Method for starting an RTS.

SC/docs/sc_FunctionalRequirements.csv

Line 113 in 52fb737

SC4003,SC4003,"Upon receipt of a Stop RTS Command, SC shall terminate the execution of the command-specified RTS table, or range of RTS table.",

Enable and disable RTS group commands requirements are missing (see SC4004, SC4005 for individual RTS requirements):

SC/docs/sc_FunctionalRequirements.csv

Lines 114 to 115 in 52fb737

	SC4004,SC4004,"Upon receipt of an Enable RTS Command, SC shall set the status of the command-specified RTS to Enabled.",
	SC4005,SC4005,"Upon receipt of an Disable RTS Command, SC shall set the status of the command-specified RTS to Disabled.",

Describe the solution you'd like
Add explicit group requirements.

Describe alternatives you've considered
None

Additional context
Allows explicit test linkage verifying the implementation relative to requirements

Requester Info
Jacob Hageman - NASA/GSFC

[skliper]

Alternatively could just make every start/stop/enable/disable RTS command a group command and eliminate the single option (just specify the range as the same RTS). Although this would break heritage use of the single version of the command.