Functional test crc results are implementation (and possibly endian) dependent, fail vs hard coded expected value

[skliper]

Is your feature request related to a problem? Please describe.
CRC calculations can depend on implementation or endianness of data being tested (test fails on MCP750 which is big endian):

cFE/modules/cfe_testcase/src/es_misc_test.c

Lines 36 to 56 in 64a6a59

	void TestCalculateCRC(void)
	{
	const char *Data = "Random Stuff";
	uint8 Data2[12];
	uint32 expectedCrc = 20824;
	uint32 inputCrc = 345353;
	uint32 expectedBlockCrc = 2688;
	UtPrintf("Testing: CFE_ES_CalculateCRC");
	UtAssert_UINT32_EQ(CFE_ES_CalculateCRC(Data, sizeof(Data), 0, CFE_MISSION_ES_DEFAULT_CRC), expectedCrc);
	memset(Data2, 1, sizeof(Data2));
	UtAssert_UINT32_EQ(CFE_ES_CalculateCRC(&Data2, sizeof(Data2), inputCrc, CFE_MISSION_ES_CRC_16), expectedBlockCrc);
	UtAssert_UINT32_EQ(CFE_ES_CalculateCRC(Data, sizeof(Data), 0, CFE_MISSION_ES_CRC_8), 0);
	UtAssert_UINT32_EQ(CFE_ES_CalculateCRC(Data, sizeof(Data), 0, CFE_MISSION_ES_CRC_32), 0);
	UtAssert_UINT32_EQ(CFE_ES_CalculateCRC(NULL, sizeof(Data), expectedCrc, CFE_MISSION_ES_CRC_16), expectedCrc);
	UtAssert_UINT32_EQ(CFE_ES_CalculateCRC(Data, 0, expectedBlockCrc, CFE_MISSION_ES_CRC_16), expectedBlockCrc);
	}

Describe the solution you'd like
Convert to MIR

Describe alternatives you've considered
None

Additional context
None

Requester Info
Jacob Hageman - NASA/GSFC