FDC3 Directory support

[johnman]

Added ability to:

specify apps in:

• FDC3 1.2 app directory format (using customConfig for additional platform specific settings)
• FDC3 2.0 app directory format (using hostManifests setting for platform specific settings)
• Updated our custom format to support an interop setting vs an intents array (both are populated at the moment for backwards compatibility)

Also updated the broker to return the right getInfo response based on whether the client is fdc3 1.2 or 2.0 and did the same for the findIntent and findIntentByContext app meta data response that come alongside the intent(s) found.

At this time the platform is pretty complaint. There are two opinionated pieces of the platform:

• the fdc3 open api does work but an app has to opt into it working by specify intent support for an Intent called OpenApp. They can then register an intent handler for that intent in order to receive the context.
• the apps returned by findIntent and findIntentByContext do not include instances (awaiting feedback on this). The reason for this is that this could be expensive if you have a lot views/windows as we generate rich app meta data for instances and it seems wasteful to collect all of that in case someone needs it. If someone wants a list of all instances there is the fdc3.findInstances api and if they wish to gather additional meta data for each instance (or a specific instance) they can use the fdc3.getAppMetadata api. This is more efficient.

[obany]

Couple of minor comments