Allow have more than one processor in an orchestrator action

Use Case

Human in the loop for Badges requires at least 3 calls to LLMProcessor:

1. Generate badge attributes based on course content
2. Regenerate just in case
3. Generate Badge json following Open Badges standard (Or any)

Our current config method with profiles don't allow to do this:

  "processor_config": {
    ...
    "LLMProcessor": {
      "function": "summarize_content",
      "provider": "qwen25"
    }
  },

With that config, if i try to call LLMProcessor two times, it will be call the same function.

  "processor_config": {
    ...
    "LLMProcessor": {
      "function": "summarize_content",
    },
  "LLMProcessor": {
      "function": "regenerate",
    },
  },

with this one, it will fail looking for a single object named with class_name

Suggested solution

Allow the profile to have many processor with a key.

{
  "processor_config": {

    "LLMProcessor": [
      {
      "summary": {
          "function": "summarize_content",
          "prompt": "summary_prompt"
          }
      },
      {
      "regenerate": {
          "function": "regenerate_response",
          "prompt": "regenerate_prompt"
          }
      }
    ]
  }
}

Then parse it as expected in the orchestrator to enable the conf of many processors.

Start by locating the orchestrator action's processor configuration parsing and the LLMProcessor handling. Trace how a single processor is selected, then determine how keyed processor definitions could be represented and invoked distinctly; done means multiple LLMProcessor configurations can be used in one action without ambiguity.