Kinds that are not partition-specific are not discoverable via Search using wildcards

Summary In the context of Schema Service providing a schema and thus a "kind" for a Storage Record, a bug has been found that prevents records from being found via Search wildcard queries on "kind" when the record "kind" does not start with the data partition name where it is resident. This is important for the very common "kind" queries applications need to perform to find relevant records.

Details Here is a specific scenario that has been observed by SLB testing:

1. records are ingested with two kinds: a) osdu:wks:master-data--Wellbore:1.0.0 and b) partition1:wks:master-data--Wellbore:1.0.0.
2. the above records (1201 count for each kind) can be found in Storage and directly via search when kind queries such as: "kind": osdu:*:*:* and "kind": partition1:*:*:* are used. So the records appear to be indexed and are searchable.
3. When wildcard queries using the first field are used, however, only the partition-based kind records are found. In this case, the query "kind"::wks::* finds only the "partition1" records -- 1201 vs. the 2402 records that are expected.