[ce] repository control plane and data plane

[ssmith-pc]

Problem

First pass implementation of control plane SDK for repositories.

Also includes a basic data plane impl that avoids using the OpenAPI generated types due to Document being such an open-ended type. More work is needed here

pc = Pinecone(api_key=os.getenv("PINECONE_API_KEY"))

repo_name = "aryn-parsed-example-8"

repo_model = pc.create_repository(
    name=f"{repo_name}",
    spec={
        "serverless": {
            "cloud": "aws",
            "region": "us-east-1",
        },
    },
    schema={
        "fields": {
            "$.parsed[*].text_representation": {
                "description": "Text representation of the chunk",
                "embedded": True,
            },
        },
    },
    timeout=300,
)

repo_model = pc.describe_repository(name=repo_name)

# data plane
repo = pc.Repository(host=repo_model.host)

document = get_document()
response = repo.upsert(
    namespace="foo",
    document=document,
    echo=True,
)

pc.delete_repository(name=repo_name, timeout=300)

Solution

Describe the approach you took. Link to any relevant bugs, issues, docs, or other resources.

Type of Change

• 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
• Infrastructure change (CI configs, etc)
• Non-code change (docs, etc)
• None of the above: (explain here)

Test Plan

Describe specific steps for validating this change.

[rohanshah18]

LGTM, I have some concerns around:

1. Using custom vs openApi generated client
2. Lack of testing

[akelch11]

looks good from a standpoint of type correctness, can't comment on SDK specific mechanics. dunder methods make sense intuitively