CFE_EVS_SendEventWithAppID design improvements wrt EID context and calling context

[skliper]

Is your feature request related to a problem? Please describe.
CFE_EVS_SendEventWithAppID is really intended to provide the EID context when an event is created from a library. Unfortunately the EID context replaces the app context info (name), which means for short events the ground does not have app context (can't tell what app generated the event). Also means filtering by app context isn't possible for these types of events, and apps really have no insight into or control over these events.

Describe the solution you'd like
Consider options to include both EID context and app context in short messages, filtering, etc. Could utilize extra bits, could add a field, etc. May even help to rename CFE_EVS_SendEventWithAppID to something that indicates overriding the EID context. Note if special bits were just reserved, this may collapse down to one API again (CFE_EVS_SendEvent), but depends on how the rest is addressed.

Describe alternatives you've considered
See above.

Additional context
Spawned from code review follow-up. Related to #1388 and #1389.

Requester Info
Jacob Hageman - NASA/GSFC

[skliper]

Note there's inconsistent use of CFE_EVS_SendEventWithAppID vs CFE_ES_WriteToSysLog based on service. SB and TBL APIs mostly use the former, the rest the later. SB has an internal function to include the FullName in the event message which includes calling context app and task name.