DRU paths directly including a schema rather than a response

[jerstlouis]

The DRU pDeploy.yaml and pProcessListDeploy.yaml are directly including the processSummary.yaml schema where a response is expected.

This causes Swagger UI validation errors:

"paths.'/processes'(post).responses.201.$ref target #/components/schemas/processSummary is not of expected type Response"

Instead, it should be including a new file like openapi/responses/processes-dru/rProcessSummary.yaml that sets up a response and then include the processSummary.yaml schema, or if this can also optionally have the inputs and outputs, the existing openapi/responses/processes-core/rProcessDescription.yaml could be used.

cc. @gfenoy @pvretano @fmigneault

[fmigneault]

The response is expected to be the summary (no inputs/outputs), but you are right it is missing the nested media-type and content properties.

[jerstlouis]

Thanks @fmigneault. In my PR I referenced rProcessDescription for now, which includes the inputs/outputs, but it's not required anyways... Should we set up a separate response that avoids adding it as a property altogether?

[fmigneault]

Yes. I think a separate response will be cleaner and easier to maintain.