Inconsistent console and server yaml files for GraphBinary serialization

Nobody has claimed this yet.

The link below to the JanusGraph users list includes a workaround. The server-side yaml files serialize the result to string, the client side conf/remote-graph-binary.yaml misses the tostring config option.

- Version: 0.6.0
- Storage Backend: inmemory
- Mixed Index Backend: None
- Link to discussed bug: [https://lists.lfaidata.foundation/g/janusgraph-users/topic/85619393](https://lists.lfaidata.foundation/g/janusgraph-users/topic/85619393)
- Expected Behavior: g.V().properties('some', 'value') returns a result
- Current Behavior: serialization exception

Steps to reproduce
1. Start gremlin-server and gremlin console
2. Make remote connection with conf/remote.yaml
3. Add vertex with a property. Check with g.V().properties('some', 'value')
4. Make remote connection with conf/remote-graph-binary.yaml
5. Repeat the query g.V().properties('some', 'value')

### Stack Trace (if you have one)
Console:
Server could not serialize the result requested. Server error - Error during serialization: java.lang.IllegalStateException. Note that the class must be serializable by the client and server for proper operation.

Compare conf/remote-graph-binary.yaml with the server-side YAML files, focusing on the serialization settings described in the issue. Reproduce the remote query g.V().properties('some', 'value') through both connections and verify that the GraphBinary configuration no longer causes a serialization exception.

Written by the indexing model from the issue text.