Fix #2862, correct app context in events

[jphickey]

---

name: FSW Code Change
about: Flight Software code changes
labels: fsw

Description of Change

Applies the same fix which was done for the table dump command to all other operations that use the same basic event-sending mechanism.

When the caller name is blank, this means it was invoked by a table services command. This changes the event to indicate it was a command rather than the "app=" empty string.

Linked Issue

Closes #2862

Requirements Impact

• Requirement ID(s):
• Requirements updated as necessary
• Existing requirements are still satisfied by this change

Testing Evidence

Example event with change:
EVS Port1 1980-012-14:25:46.50482 66/1/CFE_TBL 81: Activate,tbl=TST_TBL.TestTable01:Cannot activate table, Inactive image not Validated
(the app= part is removed because it comes from tbl services itself)

Unit Tests (UT Assert)

COSMOS Test Suite

Areas of Expertise Touched

• ASTRO
• CI/CD
• COSMOS
• Cybersecurity
• Docker
• EDS
• Git
• PSPs
• SBN
• SMP
• Tables
• TSN
• Unit Tests
• Other

---

Author Checklist

• Linked GitHub issue is referenced above
• Code has been formatted with .clang-format
• Static analysis workflows ran and passed
• Unit tests (UT Assert) updated/added to cover code changes
• Unit test workflows ran and passed
• COSMOS test suite was run; tests updated/added if relevant changes were made
• Requirements have been reviewed; updated or confirmed still satisfied (see above)
• Testing evidence is included above
• Self-review of the diff completed

---

Reviewer Checklist

• Code logic is correct and matches the stated intent
• Code is readable, maintainable, and follows project conventions (ask your lead if you are unsure of where to find these conventions)
• .clang-format has been applied
• Static analysis results reviewed and acceptable
• The change has been exercised by the unit tests (not just that tests pass — the new/changed code paths are actually covered)
• COSMOS test suite was executed against this change and results reviewed (or confirmed N/A with justification)
• Reviewer has independently verified the change behaves as described (e.g., by running the tests locally, reviewing CI output in detail, or performing additional ad-hoc testing as warranted)
• Memory safety reviewed (allocation, bounds, lifetime, stack usage)
• Requirements impact reviewed and appropriate
• Error handling is appropriate
• Appropriate Expert areas have been reviewed

Reviewer Testing Notes

[wmoleski]

All changes look good to me.