feat(ls): docs for OpenApi 3.1.0 Security Scheme object

[tim-lai]

Description

Documentation for OpenAPI 3.1.0 Security Scheme Object

Motivation and Context

Ref #1993

How Has This Been Tested?

local.

fixture:

openapi: 3.1.0
info:
  title: deref
  version: 1.0.0
components:
  securitySchemes:
    oauth2-server:
      type: oauth2
      flows:
        authorizationCode:
          authorizationUrl: 'https://some-url.com/auth'
          tokenUrl: 'https://some-url/token'
          refreshUrl: 'https://some-url/token'
          scopes:
            user: allows user resources
            admin: allows admin resources
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

Screenshots (if appropriate):

parent:

example target 1 type:

example target 2 scheme:

example target 3 bearerFormat:

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.