ogma-cli: Make cFS backend accept spec as input. Refs #252.

[ivanperez-keera]

Extend the cFS backend to accept an additional argument filename containing an input specification, as well as arguments indicating the formats of the file and the properties, as well as a pre-processor, as prescribed in the solution proposed for #252.

[ivanperez-keera]

Change Manager: Verified that:

• Solution is implemented:
  • The code proposed compiles and passes all tests. Details:
    • Build logs:
      • https://github.com/nasa/ogma/actions/runs/13233019028/job/36933117789
      • https://github.com/nasa/ogma/actions/runs/13233019026/job/36933117785
    • Build log archives:
      • logs_34150168558.zip
      • logs_34150168563.zip
  • The solution proposed produces the expected result. Details:
    The following dockerfile checks that the cFS command now accepts a spec as input file, as well as the file format and property format flags, and that a variables or handlers file are no longer required, and that the generated cFS app mentions both the property name listed in the original spec and the input required by that property, after which it prints the message "Success":

    --- Dockerfile-252
    FROM ubuntu:focal
    
    ENV DEBIAN_FRONTEND=noninteractive
    RUN apt-get update
    
    RUN apt-get install --yes \
          curl g++ gcc git libgmp3-dev libz-dev make pkg-config
    
    RUN mkdir -p $HOME/.local/bin
    ENV PATH=$PATH:/root/.local/bin/
    
    RUN curl https://downloads.haskell.org/~ghcup/0.1.17.7/x86_64-linux-ghcup-0.1.17.7 -o $HOME/.local/bin/ghcup
    RUN chmod a+x $HOME/.local/bin/ghcup
    
    ENV PATH=$PATH:/root/.ghcup/bin/
    RUN ghcup install ghc 9.10
    RUN ghcup install cabal 3.12
    RUN ghcup set ghc 9.10.1
    RUN cabal update
    
    ADD document.json   /tmp/document.json
    ADD json-format.cfg /tmp/json-format.cfg
    ADD cfs-variable-db /tmp/cfs-variable-db
    
    SHELL ["/bin/bash", "-c"]
    CMD git clone $REPO \
        && cd $NAME \
        && git checkout $COMMIT \
        && cabal install ogma-cli:ogma \
        && ogma cfs --input-file /tmp/document.json --variable-db /tmp/cfs-variable-db --app-target-dir cfs/ --input-format /tmp/json-format.cfg --prop-format literal \
        && grep -q '^position_t position;' cfs/fsw/src/copilot_cfs.c \
        && grep -q 'PositionSafe' cfs/fsw/src/copilot_cfs.c \
        && echo "Complete Success"
    
    --- document.json
    {
      "Example": {
        "internal_variables": [],
        "external_variables": [
          {"name":"position", "type":"position_t", "meaning": "Position of the vehicle"}
        ],
        "properties": [
          {
            "id":      "PositionSafe",
            "formula": "PTLTL.alwaysBeen (position # x < 100 && position # y < 100)",
            "text":    "The vehicle stays withing a rectangle with side 100 meters"
          }
        ]
      }
    }
    
    --- json-format.cfg
    JSONFormat
       { specInternalVars    = Just "..internal_variables[*]"
       , specInternalVarId   = ".name"
       , specInternalVarExpr = ".meaning"
       , specInternalVarType = Just ".type"
       , specExternalVars    = Just "..external_variables[*]"
       , specExternalVarId   = ".name"
       , specExternalVarType = Just ".type"
       , specRequirements    = "..properties[*]"
       , specRequirementId   = ".id"
       , specRequirementDesc = Just ".text"
       , specRequirementExpr = ".formula"
       }
    
    --- cfs-variable-db
    ("position", "position_t", "POSITION_MID", "Position")
    

    Command (substitute variables based on new path after merge):

    $ docker run -e "REPO=https://github.com/ivanperez-keera/ogma" -e "NAME=ogma" -e "COMMIT=5796b8aafee7f4f017e2033cc3701ae91afa6999" -it ogma-verify-252
    

• Implementation is documented. Details:
  The new code includes comments for all top-level functions. All new fields are documented, and the README is updated to explain the new fields. Old text is also updated since some arguments are no longer mandatory.
• Change history is clear.
• Commit messages are clear.
• Changelogs are updated.
• Examples are updated. Details:
  No updates needed; change does not alter the behavior of the existing examples.
• Author is internal or has provided signed CLA.
• Required version bumps are evaluated. Details:
  Bump needed; the change affects the API of ogma-core.