Jira plugin open api

[amsacha]

Motivation and Context

Provide an example implementation of connecting the Semantic Kernel to external plugins following the open api schema.

Description

Jira Open API schema usage example
Renaming the azure key vault example, so all open api skill examples are grouped together
Prevent RestApiOperationRunner.cs from wrapping a json response into a json object.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
• The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[dluc]

pls see comments about naming and docs

[cchighman]

Curious whether it makes sense to pull the openapi spec from https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json versus including the spec as part of the skill since this create a tight coupling between the version included with the skill and the current version available -- implying I assume that updates must be made here if we want to keep up to date. There's also the risk of a breaking change to Jira's API, which is less likely to happen but does happen, that might render this skill unusable for a customer in production until fix were made.

[cchighman]

Curious whether it makes sense to pull the openapi spec from https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json versus including the spec as part of the skill since this create a tight coupling between the version included with the skill and the current version available -- implying I assume that updates must be made here if we want to keep up to date. There's also the risk of a breaking change to Jira's API, which is less likely to happen but does happen, that might render this skill unusable for a customer in production until fix were made.

Perhaps it could be cached, for efficiency. There is an implicit assumption here that you would always be pulling the latest API as opposed to a specific version so maybe that link above wouldnt work. Maybe https://developer.atlassian.com/cloud/jira/platform/swagger.json is meant to always point to the latest.

[amsacha]

Curious whether it makes sense to pull the openapi spec from https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json versus including the spec as part of the skill since this create a tight coupling between the version included with the skill and the current version available -- implying I assume that updates must be made here if we want to keep up to date. There's also the risk of a breaking change to Jira's API, which is less likely to happen but does happen, that might render this skill unusable for a customer in production until fix were made.

We don't support version 3 in the semantic kernel, so we cant use the latest swagger anyway