RN(View): Remove TextAncestor provider

[ecreeth]

Summary

I think the TextAncestor provider is unnecessary in the View component as the renderer
will throw an error if it doesn't find the value in the context anyway.

Changelog

[JavaScript] [Changed] - Remove TextAncestor provider for View

Test Plan

• yarn test passed

• RNTester Android app build successful

• A View component with text must throw error: Text strings must be rendered within a <Text> component.

<View>Hello error</View>

Below we can see that all the providers of the View component have been eliminated from the component hierarchy

Before	After

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	7,004,396	-84
android	hermes	armeabi-v7a	6,667,987	-87
android	hermes	x86	7,424,689	-90
android	hermes	x86_64	7,315,583	-101
android	jsc	arm64-v8a	9,164,319	-18
android	jsc	armeabi-v7a	8,820,026	-20
android	jsc	x86	9,012,705	-9
android	jsc	x86_64	9,589,784	-41

Base commit: b0fbbe5

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: b0fbbe5

[elicwhite]

Resetting the text ancestor is required to change what kinds of Text components render (inline text nodes, or block level text nodes). We need to reset that in View as text elements inside of a View need to reset to be a block level text, not an inline text node.