Cypher language specification is confusing

Currently graphsh shows a warning whenever customers use opencypher

```
gremlin> /language opencypher
Warning: Language 'opencypher' may not be compatible with neptune. Continuing anyway.
Language switched to opencypher
opencypher> /language cypher
Language switched to cypher
cypher>
```

This should be treated identically across the stack. I think the fix is in connection.py where there is a map between DB type and language type, it needs to include opencypher (or normalize opencypher to cypher so rest of the code works as expected).

Start in connection.py, where the issue identifies the map between database and language types. Reproduce the /language opencypher and /language cypher commands in graphsh, then trace how each language is classified. Done means opencypher is treated consistently with cypher and the warning no longer appears for a compatible language.

Written by the indexing model from the issue text.