This API will be later tied to jobs as defined for specific flows
(post-training, eval, etc.) through the common scheduler mechanism.
Note: At the moment, API does nothing useful. (Except returning Not
Implemented errors when called.)
This is an alternative to developing per-flow jobs APIs. Eventually,
once /jobs API is implemented, we should be able to deprecate existing
APIs under /v1/post-training/, /v1/eval/ etc.
See #1587 (tracker)
See #1238 (design details)
Note: This is an alternative path to #1582 and #1583.
Signed-off-by: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>