feat: Add ChatGPT through the OpenAIChatCompletion transformer

[mhamilton723]

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

Briefly describe the changes included in this Pull Request.

How is this patch tested?

• I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

• No. You can skip this section.
• Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

• No. You can skip this section.
• Yes. Make sure you have added samples following below steps.

1. Find the corresponding markdown file for your new feature in website/docs/documentation folder.
   Make sure you choose the correct class estimators/transformers and namespace.
2. Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
3. Make sure the DocTable points to correct API link.
4. Navigate to website folder, and run yarn run start to make sure the website renders correctly.
5. Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
6. Make sure the WebsiteSamplesTests job pass in the pipeline.

[mhamilton723]

/azp run

[github-actions]

Hey @mhamilton723 👋!
Thank you so much for contributing to our repository 🙌.
Someone from SynapseML Team will be reviewing this pull request soon.

We use semantic commit messages to streamline the release process.
Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix.
This helps us to create release messages and credit you for your hard work!

Examples of commit messages with semantic prefixes:

• fix: Fix LightGBM crashes with empty partitions
• feat: Make HTTP on Spark back-offs configurable
• docs: Update Spark Serving usage
• build: Add codecov support
• perf: improve LightGBM memory usage
• refactor: make python code generation rely on classes
• style: Remove nulls from CNTKModel
• test: Add test coverage for CNTKModel

To test your commit locally, please follow our guild on building from source.
Check out the developer guide for additional guidance on testing your change.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[codecov-commenter]

Codecov Report

Merging #1887 (d5320a6) into master (7657089) will increase coverage by 0.01%.
The diff coverage is 95.52%.

@@            Coverage Diff             @@
##           master    #1887      +/-   ##
==========================================
+ Coverage   86.86%   86.87%   +0.01%     
==========================================
  Files         299      301       +2     
  Lines       15542    15557      +15     
  Branches      801      792       -9     
==========================================
+ Hits        13500    13515      +15     
  Misses       2042     2042              

Impacted Files	Coverage Δ
...e/synapse/ml/cognitive/form/FormRecognizerV3.scala	88.00% <ø> (ø)
...re/synapse/ml/cognitive/language/AnalyzeText.scala	95.17% <ø> (ø)
.../synapse/ml/cognitive/openai/OpenAIEmbedding.scala	80.00% <ø> (ø)
...oft/azure/synapse/ml/cognitive/openai/OpenAI.scala	81.67% <93.54%> (+0.11%)	⬆️
...pse/ml/cognitive/openai/OpenAIChatCompletion.scala	95.23% <95.23%> (ø)
...re/synapse/ml/cognitive/CognitiveServiceBase.scala	82.70% <100.00%> (+0.57%)	⬆️
...synapse/ml/cognitive/openai/OpenAICompletion.scala	93.75% <100.00%> (+25.56%)	⬆️
...ure/synapse/ml/cognitive/openai/OpenAIPrompt.scala	84.90% <100.00%> (+0.90%)	⬆️
...re/synapse/ml/cognitive/openai/OpenAISchemas.scala	100.00% <100.00%> (ø)

... and 4 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).