Identical assert repeated twice (unintentionally)

[thnkslprpt]

Checklist

• I reviewed the Contributing Guide.
• I performed a cursory search to see if the bug report is relevant, not redundant, nor in conflict with other tickets.

Describe the bug
Assert of (call_count_CFE_EVS_SendEvent == 0... seems to have been pasted twice by mistake.

Code snips

MD/unit-test/md_app_tests.c

Lines 460 to 475 in 87e0c1f

	/* Verify results */
	UtAssert_True(Result == -1, "Result == -1");
	call_count_CFE_EVS_SendEvent = UT_GetStubCount(UT_KEY(CFE_EVS_SendEvent));
	UtAssert_True(call_count_CFE_EVS_SendEvent == 0, "CFE_EVS_SendEvent was called %u time(s), expected 0",
	call_count_CFE_EVS_SendEvent);
	strCmpResult = strncmp(ExpectedSysLogString, context_CFE_ES_WriteToSysLog.Spec, CFE_MISSION_EVS_MAX_MESSAGE_LENGTH);
	UtAssert_True(strCmpResult == 0, "Sys Log string matched expected result, '%s'", context_CFE_ES_WriteToSysLog.Spec);
	call_count_CFE_EVS_SendEvent = UT_GetStubCount(UT_KEY(CFE_EVS_SendEvent));
	UtAssert_True(call_count_CFE_EVS_SendEvent == 0, "CFE_EVS_SendEvent was called %u time(s), expected 0",
	call_count_CFE_EVS_SendEvent);

Expected behavior
Removing unintentionally repeated test will make cleaner test code.

Reporter Info
Avi Weiss @thnkslprpt