Bug caused by operations that delete graphs using python

- Version: 1.0.0
- Storage Backend: inmemory
- Mixed Index Backend: elasticresearch-8.6.0
- API/Driver: Gremlin-python 3.2.6
- Steps to Reproduce:

As shown in this picture, we provide a partial code example in Python to create graph data. Lines 1-4 create a node and return its property key-value pairs. Line 7 deletes all nodes and edges from the graph. Lines 8-11 create a node with the same type but different property types and return its property key-value pairs. From the output results in lines 5 and 6, it can be seen that the property values of nodes constructed under different graph database engines are the same. From the result in line 12, it can be seen that Janusgraph creates the 'p9' property value and 'test3' property value of the node with integer and float, but displays them as float and string. Line 13 shows that Tinkergraph displays property values in a type consistent with the input during node creation. Therefore, we infer that even after deleting all nodes and edges from the graph, the property value types of the nodes initially constructed in Janusgraph will still affect the types of subsequently constructed node property value , leading to a bug.

Start by reproducing the reported Gremlin-Python sequence: create properties, delete all nodes and edges, then create properties with different types on the inmemory backend and compare the results with TinkerGraph. No source files or tests are named; done means determining whether deletion leaves prior property types affecting later values and adding a regression test for the observed behavior.

Written by the indexing model from the issue text.