Avoid assert on BufferManager destruction

[Kronos3]

Originating Project/Creator
Affected Component	Svc/BufferManager
Affected Architectures(s)	All
Related Issue(s)
Has Unit Tests (y/n)
Builds Without Errors (y/n)
Unit Tests Pass (y/n)
Documentation Included (y/n)

---

Change Description

Avoid calling BufferManager::cleanup() if BufferManager::setup() was never called.

Rationale

Relevant when FSW exits early (before initialization). The BufferManager destructor will be called and either an assertion will trip saying m_allocator is NULL or segfault if there is no assertion hook set up.

fprime/Svc/BufferManager/BufferManagerComponentImpl.cpp

Lines 65 to 74 in 582f180

	FW_ASSERT(this->m_allocator);
	if (not this->m_cleaned) {
	// walk through Fw::Buffer instances and delete them
	for (NATIVE_UINT_TYPE entry = 0; entry < this->m_numStructs; entry++) {
	this->m_buffers[entry].buff.~Buffer();
	}
	this->m_cleaned = true;
	// release memory
	this->m_allocator->deallocate(this->m_memId,this->m_buffers);