[Bug] Docker build conflates build ARGs with ENV variables

[zackproser]

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

While we probably DO need to pass in:

• PINECONE_API_KEY
• PINECONE_ENVIRONMENT
• PINECONE_INDEX

During the first build stage - because otherwise the call to new Pinecone will blow up, we do not need to set all the Postgres environment variables via build args.

Instead, we want the container to be as agnostic as possible, and to read everything it needs from the environment. This approach is compatible with ECS Fargate and the Pulumi TypeScript provider we're using to ultimately deploy these containers.

Expected Behavior

See above

Steps To Reproduce

Read

Relevant log output

No response

Environment

- **OS**:
- **Language version**:
- **Pinecone client version**:

Additional Context

No response