Searching for Substrings of the room name / number („Raumkennung“)

[BaumBanane]

Is your feature request related to a problem? Please describe.
When searching for the room 1.221 in the Hauptgebäude, searching for 1.221 will return no useful results. You either need to search for 1221 (Architektenname) or 01.221.

Describe the solution you'd like
When searching for a room, consider all superstrings of that room in the Architektenname and the Raumkennung

Describe alternatives you've considered
I have not considered any alternatives.

Additional context
Current behavior:

[CommanderStorm]

The current way the costing is done, these are our ranking rules:

NavigaTUM/server/src/setup/meilisearch.rs

Lines 68 to 76 in 1b090bd

	.with_ranking_rules([
	"words",
	"typo",
	"rank:desc",
	"proximity",
	"attribute",
	"sort",
	"exactness",
	])

The rule that would be able to help here is typo.
The reason the rooms are currently lower ranked is that

• maybe rank:desc (i.e. the rule that adds a bias for larger/more relevant "things" in searching) should have a lower priority

• maybe the type bias (i.e. a lecture hall is more relevant than ) should be spit out of rank

• I currently don't have a second pass to enable better typo searching
  => stripping leading zeros and adding this as another index to search on
  => keeping the unmodifled version around (maybe with typos disabled to aid in relevancy => only have exactness on this one?)

• The typo tolerance is currently not configured.
  Thing is about relevancy is that ther alwaysis a tradeoff. When I experimented with higher typo tolerance values, the results were worse in the "benchmark" (might be biased or not have).

  Typo on the first character Meilisearch considers a typo on a query's first character as two typos.

  I don't quite know from the top of my head what the minimum word size for one/two typos are.

In general, searching is really hard to get relevant results

[CommanderStorm]

Okay, while #1766 solved some leading zero related issues in our relevancy benchmark, it did not solve the reported issue of 1.221.
This one seems unaffected.