After `dev` ML discussion need to decide do we need to add an extra Persistance DB Index or not

Thanks for the perf. update @binarycat0 ! However, the execution times are too small and the sample size is small too (I'm afraid) so the perf. numbers are not decisive, IMHO :sweat_smile:

At the same time the new index will have some storage and maintenance overhead.

Let's open a `dev` ML discussion about this and see what people who use Polaris with Postgres think.

The java code changes LGTM :+1:

_Originally posted by @dimas-b in https://github.com/apache/polaris/issues/2465#issuecomment-3245776381_

----
As a point for adding an index, this comment can be taken:
- https://github.com/apache/polaris/pull/2465#issuecomment-3244547998

Start by reading issue 2465, the linked pull request, and the referenced performance comment. Review the proposed index's performance, storage, and maintenance trade-offs with Polaris users of Postgres; the issue is done when the discussion reaches and records a decision about whether to add it.

Written by the indexing model from the issue text.