Altering searchd.expansion_phrase_limit functionality

[KALLIAK]

Proposal:

Good day! We’ve encountered an issue with the paid customization related to the functionality: you added an option for the limit searchd.expansion_phrase_limit, which triggers an error when reached.
In our current "workaround" implementation via query preprocessing, we also have such an option. However, in our case, when the limit is reached, the remaining combination variants are simply discarded — meaning the output quality may slightly decrease, but the user does not receive an error. This is important because the user has no way to influence the number of these combinations on their side without altering the original query.
Would it be possible to modify this option so that it behaves in a similar way, or perhaps add an additional option specifying whether to return an error or truncate combinations when the limit is reached?

Checklist:

^{To be completed by the assignee. Check off tasks that have been completed or are not applicable.}

• Implementation completed
• Tests developed
• Documentation updated
• Documentation reviewed
• OpenAPI YAML updated and issue created to rebuild clients

[tomatolog]

I was sure if the expansion_phrase_limit hit the user should get the error with the text query too complex, exceeds max variants limit during OR combination (complexity %d, expansion_phrase_limit %d)

Could you provide reproducible example of the case then limit got hit but the user get back result set without error?
I need the config, table and the search query with the result you got for that query.