Replace `ruby-openai` library usage with directly Net::HTTP direct calls.

[andreibondarev]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

[khaile]

Hi @andreibondarev , Could you please provide more context? I would love to take over this.

[mvz]

I'm also curious about the context of this. Isn't this simply duplicate work?

[gmyers-aiq]

I can't speak to the original author's intent here, but there are now two competing OpenAI client libraries for Ruby:

• The newer, official one from OpenAI named openai
• The unofficial library named ruby-openai (which langchainrb uses)

I think a lot of people (myself included) will want to migrate their codebases to the official library. But unless/until this issue gets resolved, you can't functionally have both gems installed in the same project. And since langchainrb uses the latter exclusively, I think there's a good case for either supporting both—or for doing what @andreibondarev was perhaps asking for, by supporting neither, in favor of using OpenAI's REST API instead. Again, I can't really speak for him, but I think what I have outlined here is a worthy effort.