Add Functional Tests for Text Component

Test cases should be added to the E2E test app (Fabric) to validate the following functionality scenarios.

### Tasks
- [ ] Text should update upon fast refresh.
- [ ] Text font should update upon fast refresh.
- [ ] Text size should update upon fast refresh.
- [ ] Text weight should update upon fast refresh.
- [ ] Text color should update upon fast refresh.
- [ ] Text styling should update upon fast refresh.
- [ ] Text line height should update upon fast refresh.
- [ ] Text alignment should updte upon fast refresh.
- [ ] Text font style should update upon fast refresh.
- [ ] Text background color should update upon fast refresh.
- [ ] Text transform should update upon fast refresh.
- [ ] Text borders should update upon fast refresh.
- [ ] Text foreground should not be overwritten when backgroundColor is set.
- [ ] Updates to a raw text node should not overwrite the TextBlock parent if it has only a single Span child inline. #7572
- [ ] Text should be marked dirty when descendant text nodes are added or removed
- [ ] Text should also be marked dirty when descendants of descendant virtual text nodes have changes to their text content.
- [ ] A raw text update to a non-optimized Text component should not call ClearValue on the TextBlock::TextProperty #11000
- [ ] Changes to the backgroundColor prop on virtual text nodes should update their corresponding TextHighlighters. #8408
- [ ] Changes to the underlying text should update the TextHighlighter ranges #8408
- [ ] Text numberOfLines should update upon fast refresh.
- [ ] Text should trigger action upon press.
- [ ] Text should trigger action upon long press.

Start in the E2E test app (Fabric) and review its existing functional test structure for the Text component. Add coverage for the listed fast-refresh, text styling, text-node, TextHighlighter, line-count, press, and long-press scenarios. Done means the new cases pass and validate each requested behavior.