Use `size_t` for size parameters/variables

[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
A few variables/parameters representing size could be updated to the more expressive size_t typedef.

Code snips
DataLength should be size_t:

DS/fsw/src/ds_file.h

Lines 121 to 127 in 2a6c6a2

	* \param[in] FileIndex Destination file index
	* \param[in] FileData Pointer to packet data
	* \param[in] DataLength Length of packet data
	*
	* \sa #DS_AppFileStatus_t, #DS_DestFileEntry_t
	*/
	void DS_FileWriteData(int32 FileIndex, const void *FileData, uint32 DataLength);

MaxFileSize should be size_t:

DS/fsw/src/ds_table.h

Lines 353 to 357 in 2a6c6a2

	* \param[in] MaxFileSize Maximum Size Limit value
	*
	* \sa #DS_TableVerifyAge, #DS_TableVerifyCount, #DS_DestFileEntry_t
	*/
	bool DS_TableVerifySize(uint32 MaxFileSize);

...and a few other local variables.

Expected behavior
Update to size_t where possible.

Reporter Info
Avi Weiss @thnkslprpt

[chillfig]

DataLength in DS_FileWriteData() / DS_FileWriteError(). concur, size_t is a valid enhancement. It never touches a pipe or file record.

MaxFileSize in DS_TableVerifySize() and in the payload struct should stay uint32. MaxFileSize is a field in both a command payload (DS_DestSize_Payload_t) and a cFE table entry (DS_DestFileEntry_t), both of which cross serialization boundaries (SB wire format, on-disk table). size_t is platform-dependent and could break alignment on mixed architectures. DS_TableVerifySize()'s parameter should match its source type exactly.