Add or operator for Elasticsearch filters and use exists if value is null

[cewald]

Related issues

I needed a possibility to simply add an or/should filter to the quickSearchByQuery method.
This wasn't possible yet, so I extended the prepareElasticsearchQueryBody method of the ElasticSearch search-adapter to accept an or operator in the value property.
I also added an ES exists filter if the value is null if you just wan't the field to be null.

Short description and why it's useful

I had to make a product query where I wanted a collection of products with a specific value or an empty one. This wasn't possible yet because all filters are chained as 'AND' filters.

Now you can make query like this (or in the last two lines) to show all products with custom_attribute is 2 or 3 or custom_attribute is just empty (null):

let query = new SearchQuery()
query
  .applyFilter({ key: 'visibility', value: { in: [2, 3, 4] } })
  .applyFilter({ key: 'status', value: { in: [0, 1] } })
  .applyFilter({ key: 'category_ids', value: { in: [categoryId] } })
  .applyFilter({ key: 'custom_attribute', value: { or: null } })
  .applyFilter({ key: 'custom_attribute', value: { or: [2, 3] } })

In our use-case the products have clusters, so I wan't to show products to the customer which have his current cluster OR if there are not enough of them just regular products without a cluster.

With this changes I can make queries like this to the ES while I still can use all the advantages of quickSearchByQuery:

{
  "filter": {
    "bool": {
      "should": [
        {
          "terms": {
            "custom_attribute": [2, 3]
          }
        },
        {
          "bool": {
            "must_not": [
              {
                "exists": {
                  "field": "custom_attribute"
                }
              }
            ]
          }
        }
      ]
    }
  }
}

If you think it isn't an essential functionallity, just ignore and close this PR.
But I thought this might come in handy.

Which environment this relates to

Check your case. In case of any doubts please read about Release Cycle

• Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
• RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
• Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

• No upgrade steps required (100% backward compatibility and no breaking changes)
• I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change

Contribution and currently important rules acceptance

• I read and followed contribution rules

[pkarw]

Related to #3934
@andrzejewsky its a good first step to make SearchQuery extendable
I’d suggest extracting the SearchQuery2Elastic as a separate repo / non even - make it extendable and useful for both vs-api and sf-api (as it should be removed from the VS itself: #2167

[andrzejewsky]

looks good for me 👍

[andrzejewsky]

@cewald can you rebase with the current develop branch? I wanted to do this on my own but I don't have access to your repository.

[cewald]

@andrzejewsky Sorry, but I messed up this branch by rebasing it with the wrong branch (too many repos, branches and remotes :)). I re-added the changes to a clean branch and opened up a new PR #3960 so we can close this one.

[pkarw]

Thanks Christian