Factor out construction of FullName in SB event messages

[skliper]

Is your feature request related to a problem? Please describe.
CFE_SB_GetAppTskName(TskId, FullName) is called in virtually every API event message, example:

cFE/modules/sb/fsw/src/cfe_sb_api.c

Lines 235 to 260 in c8b5e00

	case CFE_SB_CR_PIPE_BAD_ARG_EID:
	CFE_EVS_SendEventWithAppID(CFE_SB_CR_PIPE_BAD_ARG_EID, CFE_EVS_EventType_ERROR, CFE_SB_Global.AppId,
	"CreatePipeErr:Bad Input Arg:app=%s,ptr=0x%lx,depth=%d,maxdepth=%d",
	CFE_SB_GetAppTskName(TskId, FullName), (unsigned long)PipeIdPtr, (int)Depth,
	OS_QUEUE_MAX_DEPTH);
	break;
	case CFE_SB_MAX_PIPES_MET_EID:
	CFE_EVS_SendEventWithAppID(CFE_SB_MAX_PIPES_MET_EID, CFE_EVS_EventType_ERROR, CFE_SB_Global.AppId,
	"CreatePipeErr:Max Pipes(%d)In Use.app %s", CFE_PLATFORM_SB_MAX_PIPES,
	CFE_SB_GetAppTskName(TskId, FullName));
	break;
	case CFE_SB_CR_PIPE_NAME_TAKEN_EID:
	CFE_EVS_SendEventWithAppID(CFE_SB_CR_PIPE_NAME_TAKEN_EID, CFE_EVS_EventType_ERROR, CFE_SB_Global.AppId,
	"CreatePipeErr:OS_QueueCreate failed, name taken (app=%s, name=%s)",
	CFE_SB_GetAppTskName(TskId, FullName), PipeName);
	break;
	case CFE_SB_CR_PIPE_NO_FREE_EID:
	CFE_EVS_SendEventWithAppID(CFE_SB_CR_PIPE_NO_FREE_EID, CFE_EVS_EventType_ERROR, CFE_SB_Global.AppId,
	"CreatePipeErr:OS_QueueCreate failed, no free id's (app=%s)",
	CFE_SB_GetAppTskName(TskId, FullName));
	break;
	case CFE_SB_CR_PIPE_ERR_EID:
	CFE_EVS_SendEventWithAppID(CFE_SB_CR_PIPE_ERR_EID, CFE_EVS_EventType_ERROR, CFE_SB_Global.AppId,
	"CreatePipeErr:OS_QueueCreate returned %d,app %s", (int)Status,
	CFE_SB_GetAppTskName(TskId, FullName));

Note for the special case in CFE_SB_DeletePipeFull it currently overloads FullName with caller and owner. Really should report both if there isn't a match. Also FullName is referenced before initialized below, but not used...:

cFE/modules/sb/fsw/src/cfe_sb_api.c

Line 378 in c8b5e00

Args.FullName = FullName;

Describe the solution you'd like
Construct FullName outside switch and use it.

Describe alternatives you've considered
Really there's inconsistent reporting in APIs (sometimes system log, sometimes events, unique message formats all over with differing info), would benefit from an overhaul. See also #1403 and related issues (#994, etc) to fix.

Additional context
Code review

Requester Info
Jacob Hageman - NASA/GSFC