Deploy process directly with CWL content

[fmigneault]

Given common-workflow-language/common-workflow-language#421 (comment)
Following types can be expected:

• application/cwl
• application/cwl+json
• application/cwl+yaml

Because Weaver can deploy and parse a body using application/ogcapppkg+json content (see Deploy description), ie:
https://github.com/opengeospatial/ogcapi-processes/blob/master/extensions/deploy_replace_undeploy/standard/openapi/schemas/ogcapppkg.yaml

And that body can minimally contain the following:

{
   "processDescription": { "id" : "<process>" },
   "executionUnit": [ { "unit": { "<CWL>" } } ]
} 

We can support direct deployment of the { CWL } portion as JSON forming the request body.

Detection should take into consideration the provided Content-Type header as per:
https://github.com/opengeospatial/ogcapi-processes/blob/master/extensions/deploy_replace_undeploy/standard/requirements/deploy-replace-undeploy/deploy/REQ_content-type.adoc

Since no merging of I/O definitions from WPS/CWL will happen in this case, more metadata should be supported to be provided directly from CWL contents. The most important is the id that will become required in this case.
Other metadata can also be considered, as per conversion recommendations in https://docs.ogc.org/bp/20-089r1.html#toc26