feat(ls): add documentation for OpenAPI 3.1.0 Link Object

[tim-lai]

Description

add documentation for OpenAPI 3.1.0 Link Object

Motivation and Context

Ref: #1987

How Has This Been Tested?

local.

fixture:

openapi: 3.1.0
info:
  title: deref
  version: 1.0.0
paths:
  /b:
    get:
      operationId: bget
      responses:
        '200':
          description: the user being returned
          links:
            address:
              # the target link operationId
              operationId: getUserAddress
              description: sample of links from docs
              parameters:
                # get the `id` field from the request path parameter named `id`
                userId: $request.path.id
    post:
      operationId: bpost
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/foo'
      responses:
        '200':
          description: returnData to bpost
          links:
            UserRepositories:
              # returns array of '#/components/schemas/repository'
              operationRef: '#/paths/~12.0~1repositories~1{username}/get'
              requestBody:
                username: $response.body#/username

Screenshots (if appropriate):

parent:

target: operationId

target: operationRef

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.