Fix #2323, Remove unnecessary asserts in TIME invalid command length UT

[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 TIME includes unnecessary asserts in invalid command length tests #2323
  • Removed asserts of command counters in the tests for commands sent with an invalid command length. Checking for CFE_UtAssert_EVENTSENT(CFE_TIME_LEN_ERR_EID) seems sufficient, and aligns TIME with the testing pattern in the other cFE modules.

Testing performed
GitHub CI actions all passing successfully (incl. Build + Run, Unit/Functional Tests etc.).
Local testing with cFS suite confirms no change to coverage.

Expected behavior changes
This simplifies the coverage tests and makes them easier to maintain. Also, TIME is now consistent with the other modules.

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

Contributor Info
Avi Weiss @thnkslprpt

[thnkslprpt]

Side note: TBL actually only tests for an invalid command length once:

cFE/modules/tbl/ut-coverage/tbl_UT.c

Lines 306 to 313 in 7479d22

	/* Test command pipe messages handler response to an invalid
	* message length
	*/
	UT_InitData();
	UT_CallTaskPipe(CFE_TBL_TaskPipe, &CmdBuf.Msg, sizeof(CmdBuf.NoopCmd) - 1, UT_TPID_CFE_TBL_CMD_NOOP_CC);
	CFE_UtAssert_EVENTSENT(CFE_TBL_LEN_ERR_EID);
	/* Test command pipe messages handler response to an invalid

TBL does not test an invalid command length for every single command like the other modules.

I wonder if a single test is considered sufficient, and if so, can the other modules also be reduced to a single test of invalid command length.