L3 - Default
I execute the upgrade module from optimize 2.X.0 to 2.Y.0
There is a new index in 2.Y.0 but there is no explicit upgrade step to create this index
This index is not present after executing the upgrade
After executing the upgrade the schema should be fully initialized to the state of the target version without the need for explicit IndexCreate upgrade steps
The upgrade module currently doesn't handle new indexes created in a given version unless an explicit migration step is added.
In order to handle this scenario automatically we should utilize the ElasticSearchSchemaManager as a last step during the upgrade.