@Jay Lin Thanks for reply! Assuming the content is in a specific language, you could use the Microsoft analyzers (e.g. en.microsoft), which normalize numbers and dates.
That would handle the thousand separator case, trailing zeroes after the decimal separator, and other variations that don't alter the number.
From your list of examples, the one that wouldn't be addressed is 1234.56 -> 1234 because that's a lossy conversion.
Check this document- Add language analyzers to string fields - Azure AI Search | Microsoft Learn. Using the /analyze endpoint in indexes is a great way to experiment and see how analyzers handle and tokenize different inputs.
Hope this helps. Let me know