Spring-ai Pinecone: provide customisable "content" and "distance" metadata field names

Currently the Pinecone vector store uses a hardcoded content and distance metadata field names that defaults to content_document and distance.

Different use-cases and production deployments may require different content or distance fields.
Therefore those fields need to be customisable, while defaulting to content_document and distance.