[YSQL] Improve performance for nested loop join execution

[tanujnay112]

Jira Link: DB-3564

Description

Currently, we only support batched nested loop joins on a clause of the form inner_table.c1 = outer_table.c1. We can extend this support to

• Conjoined simple clauses of the form inner_table.c1 = outer_table.c1 AND inner_table.c2 = outer_table.c2. ([YSQL] Support batched nested loop on conjunction clauses #14068)
• Clauses with an expression on the outer variable of the form inner_table.c1 = f(outer_table.c1). ([YSQL] Support batched nested loop joins on clauses that have expressions on the outer variables #14069)
• Fix readability of batched nested loop join explain output ([YSQL] Fix readability of batched nested loop join explain output #15366)
• The fact that we silently recheck all our IN conditions at the YSQL level cuts away potential benefits from batching. ([YSQL] yb_scan silently rechecks IN conditions that are bound to DocDB #13831)
• RPCs with IN conditions on hash key tuples need to be batched ([YSQL] Batching queries that use index lookup of elements inside an ANY array which uses only hash key component #7836)
• Make the cost model aware of batching. ([YSQL] Make the cost model aware of nested loop join batching #14240)
• We can also look into supporting batching parameters that are fed into subplans. ([YSQL] Batch parameters that are input into subplans #14071)
• Improve the performance of the TupleStore batching strategy. ([YSQL] TupleStore strategy in Batched Nested Loop is slow #14393)