Inconsistent naming between CLI flags and environment variables for HTTP configuration

[MacondoExpress]

Description:

There are naming inconsistencies between CLI flags and their corresponding environment variables for HTTP-related configuration options in args.go.

Current Behavior:

CLI Flag	Environment Variable
--neo4j-http-port	NEO4J_MCP_HTTP_PORT
--neo4j-http-host	NEO4J_MCP_HTTP_HOST
--neo4j-http-allowed-origins	NEO4J_MCP_HTTP_ALLOWED_ORIGINS
--neo4j-http-tls-enabled	NEO4J_MCP_HTTP_TLS_ENABLED
--neo4j-http-tls-cert-file	NEO4J_MCP_HTTP_TLS_CERT_FILE
--neo4j-http-tls-key-file	NEO4J_MCP_HTTP_TLS_KEY_FILE

Expected behavior:

CLI Flag	Environment Variable
--neo4j-http-port	NEO4J_HTTP_PORT
--neo4j-http-host	NEO4J_HTTP_HOST
--neo4j-http-allowed-origins	NEO4J_HTTP_ALLOWED_ORIGINS
--neo4j-http-tls-enabled	NEO4J_HTTP_TLS_ENABLED
--neo4j-http-tls-cert-file	NEO4J_HTTP_TLS_CERT_FILE
--neo4j-http-tls-key-file	NEO4J_HTTP_TLS_KEY_FILE