Remove reliance on hard coded task forms. Current plan is to introduce something on top of a task, called a "mission". A mission definition will include the inputs, a ui schema and a json document with json reference that defines how to convert the inputs into a RMF task. This conversion will be done by the api-server and the frontend will only work with missions.
Notes:
implement tooltips for each type of task too, where the schemas can be described
Copied over from https://github.com/open-rmf/rmf-web/issues/984, as this has a larger impact and involves rewrites and migrations.
Remove reliance on hard coded task forms. Current plan is to introduce something on top of a task, called a "mission". A mission definition will include the inputs, a ui schema and a json document with json reference that defines how to convert the inputs into a RMF task. This conversion will be done by the api-server and the frontend will only work with missions.
Notes:
Resolves https://github.com/open-rmf/rmf-web/issues/684