Issue #2727: Refactor System Resources OSAL Implmentation

[LeStarch]

Related Issue(s)
Has Unit Tests (y/n)
Documentation Included (y/n)

---

Change Description

Fixes issue #2727 by creating Os::Memory and Os::Cpu interfaces to support the non-filesystem aspects of SystemResources.

[github-advanced-security]

CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[LeStarch]

@thomas-bc will you review?

[LeStarch]

@bocchino will you review the use of templates here:

fprime/Fw/Types/StringToNumber.cpp

Lines 44 to 73 in 296aad0

	// Template for internal implementation only
	// \tparam T: input type (U8, I8, U64, I64)
	// \tparam Tinternal: function api type
	// \tparam F: conversion function to use
	template <typename T, typename Tinternal, Tinternal (*F)(const char*, char**, int)>
	Fw::StringUtils::StringToNumberStatus string_to_number_as_template(const CHAR* input, FwSizeType max_length, T& output, char** next, U8 base) {
	static_assert(std::numeric_limits<T>::is_integer, "Type must be integer");
	static_assert(std::numeric_limits<Tinternal>::is_integer, "Type must be integer");
	static_assert(std::numeric_limits<T>::is_signed == std::numeric_limits<Tinternal>::is_signed, "Signedness must match");
	static_assert(std::numeric_limits<T>::max() <= std::numeric_limits<Tinternal>::max(), "Invalid internal type chosen");
	static_assert(std::numeric_limits<T>::min() >= std::numeric_limits<Tinternal>::min(), "Invalid internal type chosen");
	char* output_next = nullptr;
	Fw::StringUtils::StringToNumberStatus status = string_to_helper_input_check(input, max_length, base);
	if (status == Fw::StringUtils::SUCCESSFUL_CONVERSION) {
	Tinternal output_api = 0;
	output_api = F(input, &output_next, base);
	if (output_api > std::numeric_limits<T>::max()) {
	status = Fw::StringUtils::StringToNumberStatus::INVALID_RANGE;
	output_api = std::numeric_limits<T>::max();
	}
	if (output_api < std::numeric_limits<T>::min()) {
	status = Fw::StringUtils::StringToNumberStatus::INVALID_RANGE;
	output_api = std::numeric_limits<T>::min();
	}
	output = static_cast<T>(output_api);
	}
	status = string_to_helper_output_check(status, input, output_next, next);
	return status;
	}

I can make the argument it is a safe use of templates because: the template is not exposed to users, or outside code (it is implemented in the CPP). The template is used as the implementation of a set of non-templated functions needed by the end user.

[bocchino]

I have reviewed the template usage. It looks good!