Fill out Material documentation and clarify render_priority and next_pass sorting

[clayjohn]

Partially address: #83774 (we still need to add more detail to the manual)

[AThousandShips]

Suggested change

	[b]Note:[/b] This will not impact how transparent objects are sorted relative to opaque objects or how dynamic meshes will be sorted relative to other opaque meshes. This is because all transparent objects are drawn after all opaque objects and all dynamic opaque meshes are drawn before other opaque meshes.
	[b]Note:[/b] This will not affect how transparent objects are sorted relative to opaque objects, or how dynamic meshes will be sorted relative to other opaque meshes. This is because all transparent objects are drawn after all opaque objects and all dynamic opaque meshes are drawn before other opaque meshes.

Small style nitpick (didn't just correct the spelling)

[clayjohn]

I prefer "impact" and the comma is incorrect. Thanks anyways!

[AThousandShips]

The comma breaks up the long sentence, but impact/affect is preference based

But to me the current sentence is too long and needs a pause, the comma is correct (I'm not assuming an oxford comma incorrectly) but a matter of preference

[AThousandShips]

Generally speaking "impact" is considered to be more powerful than "affect" and generally considered negative (for example docs regularly use it to refer to performance), but it's a matter of preference

[YuriSizov]

We discussed following one of the existing patterns for the first sentences of virtual methods, which may still be worth doing. But this should be a great addition already.

[YuriSizov]

Let's go forwards with this, additional style improvements can be done in a follow-up. Thanks!

[YuriSizov]

Cherry-picked for 4.1.4. (Including some changes from previous PRs updating the descriptions, since they were causing conflicts and we're invalidating translations anyway.)