Release v1.0.4: Database configuration fix + logging enhancement

This release fixes a critical configuration bug and adds helpful logging.

Changes:
- Fix: Neo4j database parameter now properly passed to driver initialization
  Previously, the NEO4J_DATABASE environment variable was read but ignored,
  causing data to be stored in the default 'neo4j' database instead of the
  configured database (e.g., 'graphiti'). This fix enables property-based
  multi-tenancy with user-specified database names.

- Enhancement: Log SEMAPHORE_LIMIT value at startup
  Helps users verify their concurrency control settings are correctly
  applied, especially useful when troubleshooting rate limit issues.

Files changed:
- src/graphiti_mcp_server.py: Use graph_driver pattern with database parameter
- src/services/factories.py: Include database in Neo4j config dictionary
- tests/test_database_param.py: Comprehensive test for database configuration

Breaking changes: None
Backward compatible: Yes

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

mcp_server/pyproject.toml

@@ -10,7 +10,7 @@ allow-direct-references = true
 
 [project]
 name = "graphiti-mcp-varming"
-version = "1.0.3"
+version = "1.0.4"
 description = "Graphiti MCP Server - Enhanced fork with additional tools by Varming"
 readme = "README.md"
 requires-python = ">=3.10,<4"