Support several "output" in the SWS application

[umeshsarkar]

Closes #46

The main change in this PR is that the application now supports several output variables in the FCL file, and the response structure has been updated to represent the result of each output variable. Everything else remains the same as before.

To better illustrate the support for several output variables, an example has been added in the ConstructionRobotAssistanceDecisionRules.fcl file. This file contains several output variables. To run this example, use the following command:

mvn spring-boot:run -D"spring-boot.run.profiles"=construction

In the previous version (which supported only a single output variable), the second element in the response JSON decisionResult was fixed. It always shows a single set of results, including a slidingDecision and a description, as shown below:

{
  "decisionStatus": "Sliding Decision Response",
  "decisionResult": {
    "slidingDecision": "HUMAN_ON_THE_LOOP",
    "description": "Human has to be informed about AI's rescheduling"
  },
  "decisionExplanation": {
    "...": "..."
  }
}

Since the current version supports several output parameters, having a single decisionResult field is now confusing, unstructured, and hard to read. To make the response more readable and structured, the decisionResult field now includes individual entries for each output variable, each with its own result set. The name of "individual entries" is coming from the defined output variable name in the FCL file. For example:

{
  "decisionStatus": "Sliding Decision Response",
  "decisionResult": {
    "suggestedWorkSharingApproach": {
      "slidingDecision": "ROBOT_AUTONOMOUSLY",
      "description": "Let the robot continue trying"
    },
    "systemAutonomousOperatingStatus": {
      "slidingDecision": "AUTONOMOUS",
      "description": "System is currently operating autonomously"
    }
  },
  "decisionExplanation": {
    "...": "..."
  }
}

Note: This implementation is an initial idea and should be discussed further.
to do: update the README

[gr-hovest-atb]

instead of decisionResult, better use slidingDecisionOutputParameters to be consistent with our input parameter naming in the JSON