Improved search capabilities

[grolu]

Added extended search capabilities

What this PR does / why we need it:
Adds more search capabilities (see below). This should solve several raised requirements (see linked issues).
Moreover, this PR introduces a search delay to prevent multiple searches to block the UI while typing.

Which issue(s) this PR fixes:
Fixes #1004 Fixes #994 Fixes #960

Special notes for your reviewer:

Release note:

Added extended search capabilities to cluster search:
- Search params are now ANDed, allowing one to refine the search
- Use quotes for exact words or phrases
- Use minus sign to exclude words that you don't want

[holgerkoser]

I would propose to go with the gmail like advanced search query syntax and use something like search-query-parser.

const searchQueryParser = require("search-query-parser")

function parseSearchQuery(query) {
  const options = {
    tokenize: true,
    alwaysArray: true,
    offsets: false,
    keywords: ["name", "infra", "seed", "from", "purpose", "version", "ticket"],
    ranges: ["date"],
  }
  return searchQueryParser.parse(query, options)
}
const query =
  'from:foo@sap.com,bar@sap.com name:delete purpose:eval date:20200503-20210501 "free text" foo -hugo';

console.log(parseSearchQuery(query))
/*
{
  text: [ 'free text', 'foo' ],
  from: [ 'foo@sap.com', 'bar@sap.com' ],
  name: [ 'delete' ],
  purpose: [ 'eval' ],
  date: { from: '20200503', to: '20210501' },
  exclude: { text: 'hugo' }
}
*/

[grolu]

@holgerkoser I thought about that, too. I started with this as an attempt to keep it simple. Idk how parsers perform; we already face huge performance issues in larger lists. We can test it, though.

[gardener-robot]

@holgerkoser You have pull request review open invite, please check

[petersutter]

add tests for the regex so that we can be sure in the future that it still works as expected in case we need to adapt it

[petersutter]

/lgtm

[holgerkoser]

\lgtm