Point package.json at pinecone-ts-client branch, adjust for breaking changes

[austin-denoble]

Problem

There are upcoming breaking changes to operations in pinecone-ts-client that impact this external app. Until the new release is actually available, it would be helpful to tie this application to the specific branch that includes the breaking changes: "@pinecone-database/pinecone": "git+https://github.com/pinecone-io/pinecone-ts-client.git#adenoble/update-data-plane-namespace-targeting".

Solution

Update package.json to pull in breaking changes via pinecone-ts-client branch (adenoble/update-data-plane-namespace-targeting).
Update calls to upsert to pass { records: [...]}.

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

Push and allow CI to run. This application will also be validated through the pinecone-ts-client CI pipeline: https://github.com/pinecone-io/pinecone-ts-client/blob/main/.github/actions/external-app/edge/action.yml#L30-L66