Make it possible to resolve intent based on output type as well as input

[kriswest]

Enhancement Request

Use Case:

Issue #432 (and associated PR #495) make it possible to return data from a raised intent. However, an application or resolver UI may wish resolve an intent based on the output Context data type, in addition to the input type, ensuring they know what data type to expect.

To do so, additional data representing this information must be added to the AppD's Application schema, while the findIntent and raiseIntent and related functions will need to take extra arguments facilitating the resolution.

Workflow Examples

For example, an application may allow the user to raise the ViewAnalysis intent, but require that data is returned encoding or referencing the analysis for inclusion within notes kept within the application. It either resolves the intent via findIntent followed by a targetted raiseIntent, or calls raiseIntent and relies on a resolver UI for resolution, and passes the extra detail on what type it expects to be returned. Only applications that can return the specified type are offered.

[kriswest]

This turned out to be difficult to add as an optional argument to the raiseIntent functions but is fine on the findIntent functions. Notes on that from the PR:

Support for this was not added to the raiseIntent APIs as:

• a second optional string argument would be a problem (that it isn't on findIntent)
• this form of resolution is likely to be performed programmatically, rather than through a resolver UI

[kriswest]

was resolved by #508