fix: queryByText and getByText match newlines and tabs properly

[pke]

Summary

This fixes #983.

New lines, that are rendered in RN as separate Lines, are wrongly normalised during testing.

const { queryByText } = render(<Text>{"Line 1\nLine 2"}</Text>)
expect(queryByText("Line 1\nLine 2")).toBeDefined()

Test plan

I have added 2 new tests to verify the fix is working.

[AugustinLF]

While I think this change makes sense, I believe it would get us away from @testing-library/react, which doesn't do such normalisation afaik. Do we think it's an ok tradeoff?

[pke]

@AugustinLF That is because React Web an RN handle whitespace in JSX differently. In RW it uses HTML whitespace policy, that is, to ignore whitespace. However, RN respects whitespace inside <Text> tags.

[mdjastrzebski]

@AugustinLF Looking at the code it seems that we should match Line1\nLine2' when Textcomponent contains the same very same text content. Before this PR we normalised text but did not normalize the the text matcher string which caused thenormalizedText === matcher` check to fail.

[mdjastrzebski]

As a general comment, regex text queries are more powerful and don't require perfect matching when using e.g. \s

[pke]

Rebased and applied suggestions from comments.

As a general comment, regex text queries are more powerful and don't require perfect matching when using e.g. \s

I know but here its important, that the formatting is matched exactly, as it has direct visual consequences in RN Text elements unlike React Web.

[mdjastrzebski]

@thymikee @AugustinLF We're looking for a second approval for this PR. Can you help?