Allow combining SearchQuerys with different configs

[Jaap Roes]

The fix for ticket #27143 (SearchQuery is not combinable using more than one & or | operators) introduced some code that raises a TypeError when trying to combine SearchQuery objects that do not share the same config.

I'm not sure if this restriction makes sense. In SQL it seems to be allowed e.g.:

SELECT to_tsquery('simple', 'working') || to_tsquery('english', 'working');
'working' | 'work'

[Jaap Roes]

I ran git bisect and technically this is a regression from commit 978a00e39fee25cfa99065285b0de88366710fad

Before that commit this works:

search.SearchQuery("foo", config="simple") | search.SearchQuery("bar", config="english")

Afterwards it doesn't

[Simon Charette]

Thanks for the bisect sleuthing here. Given this is a regression in 1.11 I'm not sure this qualifies for a backport for 2.1 at this point.

[Tim Graham]

Before merging, I'll give the original author some time to respond to the question about why the restriction was added. The patch looks fine.

[Jaap Roes]

fwiw, I think the config equality check was copied from the implementation of SearchVectorCombinable. The validity of that check there is also questioned by at least one person (see ticket #28528)

[Tim Graham <timograham@…>]

In 8a1a9194:

Fixed #29997 -- Allowed combining SearchQuerys with different configs.

Seems to be a needless restriction in
978a00e39fee25cfa99065285b0de88366710fad.