[lestarch-autobot]

Describe the contribution
Bumps two submodule pins to bring in the cFE-backed Os::Task implementation:

• libs/fprime_cfs -> ad2941e (Mirror F Prime events into cFE EVS: explicit AppID + Os_Task_Cfs (cFE ES child tasks) fprime_cfs#23): adds Os_Task_Cfs, which creates F Prime tasks as cFE ES child tasks so cFE APIs resolve the calling task's app context — mirrored F Prime events now reach cFE EVS via plain CFE_EVS_SendEvent (fixes the per-event Failed to mirror event ... 0xc2000003).
• apps/fprime_app -> 1804665 (Select Os_Task_Cfs and move topology priorities to cFS/OSAL semantics fprime_app#14): selects Os_Task_Cfs and moves topology priorities to cFS/OSAL semantics.

Merge order: this PR depends on fprime_cfs#23 and fprime_app#14 landing first (pins currently resolve through the JPL-Devin forks in the repo network).

Testing performed

1. Clean rebuild: make SIMULATION=native prep && ./do (zero errors)
2. Boot core-cpu1: clean, no asserts/task-create/mirror errors; one expected FPrimeApp.rateGroup1 task name truncated to PrimeApp.rateGroup1 warning
3. F Prime GDS: NO_OP round trips; each command prints mirrored FPRIME_APP EVS console lines (OpCodeDispatched/NoOpReceived/OpCodeCompleted); channels/events live
4. cFS GroundSystem: Enable Tlm via ci_lab:1234, packets received on to_lab:2234 (stock table)
5. fprime-cfs python helper: full boot + NO_OP via generated command page, mirrored EVS lines in its core-cpu1.log

Expected behavior changes

• Behavior Change: F Prime active-component tasks are created via CFE_ES_CreateChildTask (ES-registered) instead of raw pthreads; F Prime events are now visible in cFE EVS. Task priorities use cFS/OSAL semantics (lower = more urgent). One benign boot warning for the truncated FPrimeApp.rateGroup1 task name (OSAL OS_MAX_API_NAME limit).
• No API change in this repo.

System(s) tested on

• Hardware: PC (x86_64)
• OS: Ubuntu 22.04
• Versions: pins in this repo (cFE draco-rc5 line, fprime devel ce40e89)

Additional context
Mirrored events do not appear in the GroundSystem Event Messages page because the stock cpu1_to_lab_sub.c does not subscribe to EVS tlm MID 0x808; console/EVS output is the verification path.

Contributor Info
Michael Starch, NASA JPL (via Devin)