vectorstores: Add support for OpenAI Organization ID header in Chroma

[AshDevFr]

• Update chroma-go to the latest version (To include this PR
• Add error handling to NewOpenAIEmbeddingFunction
• Add a new property to the store (openaiOrganization) and pass it to chroma-go

The goal of this PR is to add support for the OpenAI Organization ID header in Chroma. It is already supported here by the OpenAI client in Langchain but it was missing from the chroma implementation.

PR Checklist

• Read the Contributing documentation.
• Read the Code of conduct documentation.
• Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
• Describes the source of new concepts.
• References existing implementations as appropriate.
• Contains test coverage for new functions.
• Passes all golangci-lint checks.

[tmc]

can you verify this chroma release is appropriate? cc @tazarov since #640 just went in

[tazarov]

@tmc, I've just added a new release for Chroma-go (v.0.0.2) with the OpenAI org change that @AshDevFr , pushed a few days back - https://github.com/amikos-tech/chroma-go/releases/tag/v0.0.2

@AshDevFr, do you mind updating your go.mod/sum.

[AshDevFr]

Updated the version

[AshDevFr]

@tazarov I see that the v0.0.2 does not return 2 values to NewOpenAIEmbeddingFunction.

I'll update this PR soon

[AshDevFr]

It should be good to go.

[tazarov]

@AshDevFr, yeah, sorry about that. Since this was a breaking change I wanted to move it to 0.1.x tag.

[tmc]

great! Can we make this "OpenAI" vs "OpenAi" in terms of exposed interface to be more consistent with existing code? (with that it can go in). (also needs rebase)

[AshDevFr]

Do you mean changing WithOpenAIOrganizationID to WithOpenAiOrganizationID in chroma-go?

chroma-go uses OpenAI and langchaingo uses OpenAi in chroma.go for function names.

I don't mind refactoring the chroma.go file to use OpenAI if you want.

[tmc]

we should be using "OpenAI" instead of "OpenAi"

[AshDevFr]

Ok I changed the whole Chroma interface to only use OpenAI instead of OpenAi but it will introduce a breaking change.

[tmc]

We could be really careful and alias and deprecate it but I think release notes will suffice. Once we get larger and more popular we can be more delicate with backwards incompatible changes.

[tmc]

LGTM