Add plugin task type inference workflow

[keithmanville]

Add a new workflow endpoint for inferring the types of a plugin task.

POST /workflows/pluginTaskProposal {"plugin_file": "contents"}

This feature should use #443 to infer parameter type names. From this it should query the database for matching names to propose existing types in the database along with missing types and the proposed data that can be used to create the type.

The response should be something like:

{
  task_name: {
    "inputParams": { name: { "proposed_types": [resource_id: int, ... ], "missing_type": PluginParameterTypeSchema } ... } }, 
    "outputParams": [{ "proposed_types": [resource_id: int, ... ], "missing_type": PluginParameterTypeSchema } , ...] }
   }, ...
}

You should always get either a proposed_type or a missing_type -- might need to further specify this when we get to implementing fuzzy matching.

This feature should build off of #443

This feature will be implemented in three separate stages:

Tasks

• Add a plugin task type inference workflow for missing types #691
• Add a plugin task type inference workflow for proposed types #692
• Expand the proposed types inference workflow to handle fuzzy matching #693