Separate GSP endpoint configuration from SPARQL query endpoint

[Copilot]

SPARQL database connections currently use the same URL endpoint for both query operations and Graph Store Protocol (GSP) operations. This change allows configuring GSP operations to use a different endpoint.

Changes

• sparql_driver(): Added optional _gsp_endpoint configuration parameter with fallback to _endpoint
• _remote_sparql_store_protocol(): Updated all GSP operations (publish, put, post, delete) to use store.gsp_endpoint instead of store.query_endpoint
• Backward compatibility: Existing configurations without _gsp_endpoint continue working unchanged

Configuration

# In system.conf or kgapp configuration
KNOWLEDGE_ENDPOINT = 'http://localhost:3030/knowledge/sparql'
KNOWLEDGE_GSP_ENDPOINT = 'http://localhost:3030/knowledge/data'  # optional

ADMIN_ENDPOINT = 'http://localhost:3030/admin/sparql'  
ADMIN_GSP_ENDPOINT = 'http://localhost:3030/admin/data'  # optional

When KNOWLEDGE_GSP_ENDPOINT or ADMIN_GSP_ENDPOINT are omitted, the system defaults to using the respective _ENDPOINT value for GSP operations.

Original prompt

Currently, the SPARQL database connections use the same URL endpoint for both query operations and SPARQL Graph Store Protocol. Please break out the GSP configuration so that it can be configured to a different endpoint URL. Start by describing a plan of action, including incorporating new tests.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[github-actions]

✅ Python tests completed! Coverage reports available in artifacts.