/flows, so every path in the reference is relative to
https://<your-domino-hostname>/flows.
Domino vendors Flyte rather than authoring it, so these endpoint descriptions
come from the upstream Flyte project. Two parts of the REST surface Flyte
actually serves are absent from the specification it publishes, and so from
this reference:
/api/v1/dataproxy/artifact_urn, and the SignalService
operations.