Moved relevance query to default query value

[indykoning]

This pr adds the ability to override the relevanceQueryMatch by using it as the default value.
Also moved this functionality to the mixin, so it can be used for the autocomplete as well as the listings

Also removed the array return value by default, keeping it backwards compatible. However if you want to set multiple queries in your callback you should exlicitly define it's behaviour by wrapping it in e.g. bool.should:

    return {
        'bool': {
            'should': [
                {
                    'neural': {
                        'content_embedding': {
                            'query_text': query,
                            'model_id': '...',
                            'min_score': 1.0,
                        }
                    }
                },
                Vue.prototype.relevanceQueryMatch(query, searchAttributes, config?.fuzziness)
            ],
            "minimum_should_match": 1
        }
    }

As you might guess, this also prepares for neural searching

[indykoning]

We could still move this to the getQuery function, removing the ability to remove/move the relevanceQueryMatch which hasn't been an ability yet until now.

[Jade-GG]

I don't necessarily mind this approach, but now if you want to add an extra query to this (for example, some kind of extra scoring function) you will also need to re-define this functionality inside of the prop. Seems a bit unwieldy to me for those cases.

Might be better in practice to have a prop that lets you disable the default query?

[indykoning]

This check just makes sure it's backwards compatible with the old way of returning an array of queries instead of a query on it's own

[royduin]

Seems like the category positions aren't working anymore

[indykoning]

I have discarded the changes, it was a fix for an issue that only seems to occur locally

[royduin]

This also depends on searchkit/searchkit#1411 right?