Fix #2811, close tbl file descriptors

[jphickey]

---

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

Description of Change

Ensure that if CFE_TBL_TxnOpenTableLoadFile() returns success, that the path always calls OS_close() before returning.

Linked Issue

Closes #2811

Requirements Impact

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

Testing Evidence

Confirmed OS_close is called during table load

Unit Tests (UT Assert)

All tests pass. Includes additional test cases to confirm that OS_close is correctly called for all of the CFE_TBL_LoadCmd tests.

COSMOS Test Suite

N/A

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