Allow complex filtering on the code (startswith, endswith, contains, regex)

[raphodn]

Story

For Open Prices - https://github.com/openfoodfacts/open-prices - when adding prices, we sometimes struggle to read the barcodes on our proof images. See related Slack discussion here

A feature that would help is additional filtering on the code field, such as :

// pseudo-code (dunno how it would translate into Lucene ^^)
search?code__startswith=123456
search?code__endswith=890
search?code__contains=45678
search?code__match=X000X00179X64

Examples

Image	Query
	search?code__match=X000X00179X64
	search?code__contains=81714&brand=Picard

[alexgarel]

@raphodn in my refactor PR, I added better support for wildcard.

So as long as you have a keyword field (like the code) you will be able do:

• code:123456*
• code:*890
• code:*45678*
• code:*000*00179*64

For regexp matching I don't remember if luqum supports it and I'm not sure if it's a good idea to activate it ;-) (I have to re-read ES considerations on it, we could maybe also make it configurable, so that it's activated only on certain field (thanks to luqum it's easy to check for that)).

[raphodn]

Did a quick test :

https://search.openfoodfacts.org/search?q=code:*81714*
// 113 hits..

https://search.openfoodfacts.org/search?q=code:*81714* brands:picard
// 1 hit :)