Could simplify by just managing tables periodically vs by registering for command (unique approach across common apps)

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I reviewed the README file to see if the feature is in the major future work.
• I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
For the standard 10 apps, SC is the only one to use the CFE_TBL_NotifyByMessage API and manage tables on command.
https://github.com/nasa/SC/blob/68e2520da89f3157703ced2467b50a34b519ca36/fsw/src/sc_app.c#L606-L612
https://github.com/nasa/SC/blob/68e2520da89f3157703ced2467b50a34b519ca36/fsw/src/sc_cmds.c#L683-L685
https://github.com/nasa/SC/blob/68e2520da89f3157703ced2467b50a34b519ca36/fsw/src/sc_cmds.c#L721-L731

Describe the solution you'd like
Could instead just periodically manage all the tables (like all the rest).

Describe alternatives you've considered
None

Additional context
None

Requester Info
Jacob Hageman - NASA/GSFC

Start by reading the table-notification and command-handling references in fsw/src/sc_app.c and fsw/src/sc_cmds.c, especially the cited lines using CFE_TBL_NotifyByMessage. Compare the current command-driven flow with the requested periodic management of all tables. Done means table management no longer depends on registration for a command and instead runs periodically, consistently with the other standard apps.