Janus 1.1 upgrade from 0.6.4 - Drop step executes, transaction commited, but vertex still exists.

Running the drop() step against a vertex executes without errors.
Then transaction committed.
Login again to Gremlin CLI and the vertex load with its properties.

- Version: Upgraded from 0.5.3 to 0.6.1 to 0.6.4 to 1.1.
- Storage Backend: Hbase 2.4.17
- Mixed Index Backend: Solr 8.11.2
- Link to discussed bug: https://github.com/JanusGraph/janusgraph/discussions/3689
- Expected Behavior: Drop vertex so it cannot be loaded.
- Current Behavior: Old Vertex still accessible with properties after Drop step. All vertexes affected from 0.6.4 and earlier. New vertex created in 1.1 not affected - works correctly.
- Steps to Reproduce:
Not reproducible in new labs, not reproducible with New vertex in Janus 1.1 on the problematic graph.
Only occurs on old large graph, recreating the graph is unrealistic. Its over 800GB large.
### Stack Trace (if you have one)
No errors or exceptions.

Tested switching query.batch.drop-step-mode=none as per release notes. No difference in behavior.
Testing also Janusgraph 1.0 with the same graph.

Start with the linked discussion at github.com/JanusGraph/janusgraph/discussions/3689 and compare behavior on the affected legacy graph under JanusGraph 1.0 and 1.1. Check query.batch.drop-step-mode=none and confirm that, after committing a drop() operation, previously created vertices no longer load with their properties; reproduction on the old graph is required.

Written by the indexing model from the issue text.