not doing the same matching* as Helm already does

[danielkrizian]

Especially since:
a) helm-q does four times the number of regex calls for that;
b) helm-q does > only a subset of Helm's matching, and
c) helm-q's matching is called after Helm's, so is guaranteed to run on items that don't match its criteria, with the number of items likely being the majority of the 15000.

• matching on the main parameters of the connection, which are displayed in the results: address, region, environment and service—since Helm does its matching on the string merged from these params. So it remains for helm-q to check only the tables, columns, functions and variables, which are normally hidden from view and thus are untouched by Helm.