Prefer use of resourceUuid index over resourceType when selecting from resourceentity table (#2739)

* Remove resourceType when searching with resourceUuid

* Remove inOrder assertion for search results not sorted

* Fix NumberSearchParameterizedTest with correct query

* Add SearchResultCorrespondenceUnorderedIncludeRevInclude

Switching from resourceType multi-column index to resourceUuid, the order of results in include/revInclude
is no longer predictable since the resourceUuids are randomly generated, also saved in the db as blob and
hence ordered by byte representation of the resourceUuid

* Refactor filterStatement to include ifBlank

* Revert add Unit type in DatabaseImplTest test methods

---------

Co-authored-by: Benjamin Mwalimu <[email protected]>

Author: LZRS