Discrepancies between the documentation and the API for FDC3 2.2

[kruplm]

Minor Issue

Area of Issue

• App Directory
• API
• Context Data
• Intents
• Desktop Agent Bridging
• Use Cases
• Other

Issue Description

There are discrepancies between the documentation and the API.

1. Agent Bridging - Find intent Example link
   
   In the payload appIntent should be "intent: { "name": StartChat}" instead of "intent: { "appId": StartChat}"

2. Agent Bridging - Step 3. Handshake & Authentication link
   DesktopAgentBridging boolean property is not included in the documentation

[SeeWhatsOn]

I think Agent Bridging - Step 3. Handshake & Authentication link
DesktopAgentBridging boolean property is not included in the documentation

refers to optionalFeatures:

  readonly optionalFeatures: {
            /** Used to indicate whether the exposure of 'originating app metadata' for
             *  context and intent messages is supported by the Desktop Agent.*/
            "OriginatingAppMetadata": boolean;
            /** Used to indicate whether the optional `fdc3.joinUserChannel`,
             *  `fdc3.getCurrentChannel` and `fdc3.leaveCurrentChannel` are implemented by
             *  the Desktop Agent.*/
            "UserChannelMembershipAPIs": boolean;
          }

It should match:

https://fdc3.finos.org/docs/api/ref/Metadata#implementationmetadata

 readonly optionalFeatures: {
    /** Used to indicate whether the exposure of 'originating app metadata' for
     *  context and intent messages is supported by the Desktop Agent.*/
    readonly OriginatingAppMetadata: boolean;
    /** Used to indicate whether the optional `fdc3.joinUserChannel`,
     *  `fdc3.getCurrentChannel` and `fdc3.leaveCurrentChannel` are implemented by
     *  the Desktop Agent.*/
    readonly UserChannelMembershipAPIs: boolean;
    /** Used to indicate whether the experimental Desktop Agent Bridging
     *  feature is implemented by the Desktop Agent.*/
    readonly DesktopAgentBridging: boolean;
  };