decouple QuickSearch from "extended" server configs

[justincorrigible]

Currently, depending on the extended parameters for the server, the QuickSearch field looks through indicated fields, relying on a single primary key field.
However, this brings three issues up:

• it requires changing global server settings for a single component, using up to two non declarative parameters (i.e. primaryKey, quickSearchEnabled), which do not clearly state they're connected, and how they operate once enabled.
• this limits the component to have shared global settings, meaning the QuickSearch will not support multiple instances of it with different field groups to search by.
• the reliance on global parameters limits implementation flexibility. searching is a local ui concern, not a global server one.