[BUG] Fix broken backward compatibility from 2.7 for IndexSorted field indices

[gashutos]

Description

Upgrade to OpenSearch 2.7 is breaking with change #6424 . Not for all scenarios but when any index contains IndexSorted field of either BYTE, BOOLEAN, SHORT, INTEGER, where the IndexSortField we created in prior version was upcasted to LONG for all above types, which was removed in #6424 to achieve better performance for sort queries.
The SortField for IndexSort is stored in SegmentInfo and that gets retained when index is migrating from old cluster to new 2.7 cluster, and hence in IndexWriter creation, Lucene throws Excetion because on 2.7, IndexWriteConfiguration has IndexSort with non-upcasted type while in SegmentInfo Lucene finds the same sort field with up-casted.

i.e, check below scenario, where Index sort is on Integer field, and the index is migrating from older version to 2.7 version, and on newer version, the IndexWriterCreation fails with IndexSort mismatch between IndexWriteIndexSort & Lucene segmentinfo contained indexsort.

"sort" : {
          "field" : "position",
          "order" : "desc"
        },
"position" : {
          "type" : "integer"
        },


Caused by: RemoteTransportException[[d3aea48e6d44f0fc824a9051f26d9969][:9300][internal:index/shard/recovery/prepare_translog]]; nested: IllegalArgumentException[cannot change previous indexSort=<sortednumeric: "position">! missingValue=-9223372036854775808 selector=MAX type=LONG (from segment=_8g9x(9.4.2):C61519:[indexSort=<sortednumeric: "position">! missingValue=-9223372036854775808 selector=MAX type=LONG]:[diagnostics={os=Linux, os.version=5.10.149-133.644.amzn2.aarch64, timestamp=1694560481039, mergeMaxNumSegments=-1, lucene.version=9.4.2, source=merge, os.arch=aarch64, java.runtime.version=11.0.18+10-LTS, mergeFactor=4, java.vendor=Amazon.com Inc.}]:[attributes={Lucene90StoredFieldsFormat.mode=BEST_SPEED}]:fieldInfosGen=36:dvGen=36 :softDel=27709 :id=5gdgx085ys6f3xyyb68rpx85c) to new indexSort=<sortednumeric: "position">! missingValue=-2147483648 selector=MAX type=INT];
Caused by: java.lang.IllegalArgumentException: cannot change previous indexSort=<sortednumeric: "position">! missingValue=-9223372036854775808 selector=MAX type=LONG (from segment=_8g9x(9.4.2):C61519:[indexSort=<sortednumeric: "position">! missingValue=-9223372036854775808 selector=MAX type=LONG]:[diagnostics={os=Linux, os.version=5.10.149-133.644.amzn2.aarch64, timestamp=1694560481039, mergeMaxNumSegments=-1, lucene.version=9.4.2, source=merge, os.arch=aarch64, java.runtime.version=11.0.18+10-LTS, mergeFactor=4, java.vendor=Amazon.com Inc.}]:[attributes={Lucene90StoredFieldsFormat.mode=BEST_SPEED}]:fieldInfosGen=36:dvGen=36 :softDel=27709 :id=5gdgx085ys6f3xyyb68rpx85c) to new indexSort=<sortednumeric: "position">! missingValue=-2147483648 selector=MAX type=INT
        at org.apache.lucene.index.IndexWriter.validateIndexSort(IndexWriter.java:1208)
        at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1119)
        at org.opensearch.index.engine.InternalEngine.createWriter(InternalEngine.java:2437)
        at org.opensearch.index.engine.InternalEngine.createWriter(InternalEngine.java:2425)
        at org.opensearch.index.engine.InternalEngine.<init>(InternalEngine.java:305)
        at org.opensearch.index.engine.InternalEngine.<init>(InternalEngine.java:223)
        at org.opensearch.index.engine.InternalEngineFactory.newReadWriteEngine(InternalEngineFactory.java:43)
        at org.opensearch.index.shard.IndexShard.innerOpenEngineAndTranslog(IndexShard.java:2286)
        at org.opensearch.index.shard.IndexShard.openEngineAndSkipTranslogRecovery(IndexShard.java:2259)
        at org.opensearch.indices.recovery.RecoveryTarget.lambda$prepareForTranslogOperations$1(RecoveryTarget.java:256)

This fix we need to release as patch release for >=2.7 versions.