Update azure.openai.chat connector

[JayaniH]

Description

Updates the azure.openai.chat connector to support the new API version with function calling capabilities and chat extensions.

Fixes https://github.com/wso2-enterprise/choreo/issues/24117

One line release note:

• Update azure.openai.chat connector to support API version 2023-08-01-preview

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Locally tested the existing and new functionality.

Test Configuration:

• Ballerina Version: 2201.7.2 (Swan Lake Update 7)
• Operating System: macOs Monterey
• Java SDK:

Checklist:

Changes to OpenAPI definition

• Modified info section of the OpenAPI definition file - Example

  • description - what the connector is about
  • x-ballerina-init-description OpenAPI extension - connector initialization details
  • x-ballerina-display OpenAPI extension - connector name and path to the connector icon

• Added proper description each API Key, if API Key authentication is defined in OpenAPI definition file

Changes to connector module

• Added license header at the top of each .bal file.
• Added Package.md as per the guide here
• Added Module.md for the module of the connector as per the guide here
• Added connector icon to the root of the connector. Icon needs to be a png of 200x200 px size with name icon.png
• Added Ballerina.toml file with following information. For keywords refer to guide

Verifying connector module

• Compiled the connector successfully with the targeted ballerina version.
• Conducted smoke tests on the connector (Recommended when OpenAPI definition is obtain from an unofficial source)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

[LakshanSS]

public types should have documentation. If the openapi spec is written by us, shall we add the documentation there and generate the connector again?

[JayaniH]

the spec is not written by us. however, we can relevant descriptions to the spec if needed.

[NipunaRanasinghe]

LGTM