Added Conversation API to JS SDK

[ConstantinChirila]

Description

This PR adds comprehensive support for the Dapr Conversation API to the JavaScript SDK, enabling developers to interact with Large Language Models (LLMs) through Dapr's conversation components. The implementation includes both HTTP and gRPC protocols, complete type definitions, and a working example.

Issue reference

#706

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release-1.16@26b3527). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff               @@
##             release-1.16     #712   +/-   ##
===============================================
  Coverage                ?   54.84%           
===============================================
  Files                   ?       14           
  Lines                   ?      330           
  Branches                ?       66           
===============================================
  Hits                    ?      181           
  Misses                  ?      131           
  Partials                ?       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[WhitWaldo]

This looks great - thank you for putting all of this together. I just updated the protos to 1.16 on the repo in master. Could you update your PR to ensure all the test pass so we can merge this in for the release?

Thank you!

[WhitWaldo]

One more thought - I don't think we need both an HTTP and a gRPC implementation as the SDK need only do one of them (typically preferring gRPC as it's typically the more complicated one).

[ConstantinChirila]

One more thought - I don't think we need both an HTTP and a gRPC implementation as the SDK need only do one of them (typically preferring gRPC as it's typically the more complicated one).

So should I remove the HTTP implementation?

[WhitWaldo]

Looks good to me - thank you very much for putting this together!

[marcduiker]

@holopin-bot @ConstantinChirila Thank you! Here's a digital badge as a small token of appreciation.

[holopin-bot]

Congratulations @ConstantinChirila, the maintainer of this repository has issued you a badge! Here it is: https://holopin.io/claim/cmi4hugl40003if045jz82xxs

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!