#7404 improve performance findCurrentVerionsByResourcePidsAndFetchResourceTable

[esecules]

improve performance of findCurrentVerionsByResourcePidsAndFetchResourceTable by using hfj_resource in the where clause that deals with resource ids to make more efficient use of the primary key

Resolves #7404

Query plan improves from one that needs to examine all history versions of all resources in the query to one that uses the existing indexes efficiently to reduce the disk IO required.
(Used SELECT * for conciseness, but in reality, it is verbosely selecting what looks like all columns from each table.)
EXPLAIN ANALYZE from current code

EXPLAIN ANALYZE of proposed solution: hfj_resource.res_id should be in the WHERE IN condition

[esecules]

When i analyze query plans it's somewhere between 2 to 5 times faster when the data is random access, and there are probably page faults, when I rerun the queries the proper query can get closer to 10x faster.

Filter on hfj_res_ver.res_id 100 random resource ids:

Filter on hfj_res_ver.res_id 100 random resource ids (second attempt):

Filter on hfj_resource.res_id 100 random resource ids:

Filter on hfj_resource.res_id 100 random resource ids (second attempt):