Don't consider typo rule on numbers

[macraig]

Feedback from @JamesToothill in meilisearch/meilisearch#3999

Feature description
When you have typo tolerance enabled with a oneTypo setting (in our case of 4), numeric typos are always considered.

This means a search for example for:

"2001"

Gets results such as:

"2001: A Space Odyssey"
"2001: A Space Travesty"
"Dracula 2000"
"Fantasia 2000"

Current behaviour
Steps to reproduce the behaviour:

1. Use an index with data that has years in the (searchable) title.
2. Set the oneTypo setting to 4 (or less)
3. Search for a year

Expected behavior
Algolia has a setting to disable this behaviour allowTyposOnNumericTokens which is default true but which we would set to false.

This allows us to search for:

"2001"

And get results such as:

"2001: A Space Odyssey"
"2001: A Space Travesty"

But not irrelevant results such as:

"Dracula 2000"
"Fantasia 2000"

Meilisearch version:
v1.2.0

[ManyTheFish]

Hello @macraig,
A potential implementation could be:

• makes charabia detect the number
• On the search side, removing the allowed typos when generating the Querytree when a word is detected as a number

This would allow us in the future to index numbers differently when tokenizing documents with Charabia during the indexing process

[thePanz]

Note: for some searches, a typo on a number is expected and should be allowed.

An example case is searching for ZIP codes

[macraig]

A potential broader solution could be to enable/disable typoTolerance as needed: https://github.com/orgs/meilisearch/discussions/727