Currently JIT executor supports only 1 DMN model resource.
A multiple DMN resources payload is required for DMN model importing other DMN models.

Goals

• support a multiple DMN models variant of the payload for the JIT endpoints; this is helpful for the use-case where the main model to be evaluated has some DMN-import references to other DMNs

Non-Goals

• internal heuristics for the resources being sent (eg: filter our non-needed resources).
  these are /dmn endpoints that works only for DMN related evaluations and analysis
• performance optimisations (as naturally sending 100s of DMN model at-once will take more time for the JIT build)