With Neo4j version 4.4, you can indeed create and drop range indexes for migration purposes.
However, it's important to note that these indexes cannot be utilized in queries yet for Neo4j 4.4.
The reason behind this is to allow the new indexes to be populated by Neo4j v4.4 before migration and to avoid any performance issues when Neo4j v5 drops the BTREE indexes.
The purpose of creating these range indexes is to have an equivalent of the binary tree index during migration to 5.x, but they won't be actively used for query optimization.
You can find further details about this in our official documentation here: Link to the documentation on indexes and future indexes.