[FEATURE] Unify LuceneEngineKnnVectorQuery and NativeEngineKnnVectorQuery within KNNQuery

[kotwanikunal]

Is your feature request related to a problem?
Coming in from #2115 - based on the discussions in the thread, we can unify LuceneEngineKnnVectorQuery and NativeEngineKnnVectorQuery to the common KNNQuery class. Currently, the KNNQuery class acts as a factory with the variations having common code between implementations,

What solution would you like?
Reduce code duplication across classes and unified scoring across engines would be ideal.
Additional aspects covered #2115 (comment)

With #2305 - we will optimize the Lucene queries in the meanwhile to improve performance and reduce rework.
To further develop a maintainable codebase, we can add in the recommended solution on top of the changes from #2305 and #2283 and streamline vector based queries.

What alternatives have you considered?

• N/A

Do you have any additional context?

• [FEATURE] Improving Lucene Engine Query Performance by reducing number of times a single Lucene k-NN query gets executed #2115